It seems currently not possible to install the Dokuwiki application.
Tried both software center and command line. The image seems not to be available anymore?
Also the link (https://github.com/bitnami/bitnami-docker-dokuwiki) to the image ns8-dokuwiki page gives an 404.
Add to module/dokuwiki8 environment DOKUWIKI_IMAGE=docker.io/bitnami/dokuwiki:20240206-debian-12
<7>podman-pull-missing docker.io/bitnami/dokuwiki:20240206-debian-12
Trying to pull docker.io/bitnami/dokuwiki:20240206-debian-12...
Error: initializing source docker://bitnami/dokuwiki:20240206-debian-12: (Mirrors also failed: [ghcr.io/nethserver/docker.io/bitnami/dokuwiki:20240206-debian-12: Requesting bearer token: invalid status code from registry 403 (Forbidden)]): docker.io/bitnami/dokuwiki:20240206-debian-12: reading manifest 20240206-debian-12 in docker.io/bitnami/dokuwiki: errors:
denied: requested access to the resource is denied
unauthorized: authentication required
Traceback (most recent call last):
File "/usr/local/agent/bin/podman-pull-missing", line 35, in <module>
subprocess.run(['podman', 'pull', image_url]).check_returncode()
File "/usr/lib/python3.11/subprocess.py", line 502, in check_returncode
raise CalledProcessError(self.returncode, self.args, self.stdout,
subprocess.CalledProcessError: Command '['podman', 'pull', 'docker.io/bitnami/dokuwiki:20240206-debian-12']' returned non-zero exit status 125.
Traceback (most recent call last):
File "/usr/local/agent/actions/create-module/05pullimages", line 48, in <module>
agent.run_helper('podman-pull-missing', *images).check_returncode()
File "/usr/lib/python3.11/subprocess.py", line 502, in check_returncode
raise CalledProcessError(self.returncode, self.args, self.stdout,
subprocess.CalledProcessError: Command '('podman-pull-missing', 'docker.io/bitnami/dokuwiki:20240206-debian-12')' returned non-zero exit status 1.
A patched dokuwiki app that pulls the archived image is available from my github. It can be used as a workaround to install dokuwiki until it’s fixed.
I think it’s also usable for testing the upgrade to the new fixed version that uses the official DokuWiki image.
Thanks for your efforts.
Obviously i had to move over the dokuwiki-data directory from the old node and set the permissions accordingly.
Anyhow, before i discovered you reply, i did test some other methods.
I restored (well partly) the backup i had, that would give the NS8 user for the app. The i fetched the images from the old node with podman save and loaded it into the new NS8 user with podman load, hoping NS would take the existing image, unfortunately that did not happen.
I also tried to podman load the images as root and tried a restore, but still no luck.
So NS8/podman restore insists on fetching images from the original image repository.
One important takeaway form this is that in case the original image source is not available at time of restore, it will fail. Even if do a disaster recovery as described in the manual, apps depending on these images will fail to restore.
Just tried the override option, this does not seem to work.
When installing the app from the app center, it still wants to pull from the original source.
Interestingly enough on the same manual page you refer to says:
If the given image is already present in the local Podman storage, no remote download occurs and the local image is used instead.
So once again i tried to podman load the images and then tried to install the app from the command line via add-module, and this works similar to your workaround.
Still that only gives you an unconfigured instance, but at least you are a step closer.
For a simple app like dokuwiki that is not to hard to do the configuration manually restore the data. For a more complex app… well not so fun i would imagine.
Maybe developers could look at the restore procedure and take existing images into account instead if insisting a pull every time. If add-module can do it, then it should also be possible to make it work for the restore.
yes it is an hidden feature, once installed from stable you can do a right click and install the testing version or do in your terminal add-module ghcr.io/nethserver/dokuwiki:1.0.6-dev.1
2025-08-01T15:22:07+02:00 [1:dokuwiki3:agent@dokuwiki3] agent.ldapproxy: domain xxx.com should not be used by dokuwiki3. Invoke agent.bind_user_domains(["xxx.com"]) to fix this warning.
2025-08-01T15:22:59+02:00 [1:dokuwiki3:dokuwiki] AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 10.0.2.100. Set the 'ServerName' directive <mark>global</mark>ly to suppress this message
It seems I can not enable the upgrade plugin. The upgrade plugin is a default plugin bundled with standard dokuwiki. The wiki logs neither the Nethserver app logs show someting interesting/related. I removed the plugin and re-installed. Same issue, can not enable it.
The screenshot is when I click ‘enable’. Can somebody test please?
When i start to install a plugin, i get this message:
No connection could be established to the plugin directory. Make sure that the server is allowed to connect to www.dokuwiki.org ans check your settings.
