Migrating Dokuwiki to NS8?

[danb35 (Dan)]

OK, next step in the migration: Dokuwiki. To the best of my recollection, Dokuwiki is a flat-file system, so migration should be as simple as copying the files over (tar them up on the NS7 system, untar them into the right directory on NS8). In case it matters, I’m using Dokuwiki’s own authentication; I’m not linking it to NS’s accounts provider. Questions:

• Am I right that this is all I need to do?
  • …and if not, what else?
• Where on the NS8 server do the files need to go?

[mrmarkuz (Markus Neuberger)]

@danb35

Am I right that this is all I need to do?

Yes, see also faq:servermove [DokuWiki]

@danb35

Where on the NS8 server do the files need to go?

On NS8 the files are in the Dokuwiki container in /bitnami/dokuwiki.

I recommend to copy the dokuwiki data from the dokuwiki user environment so you don’t need to care about permissions:

Enter the dokuwiki environment (in this example “dokuwiki1” is used, please replace it with the instance name of your dokuwiki installation):

runagent -m dokuwiki1

To upload the untarred dokuwiki folder to the container:

podman cp dokuwiki dokuwiki:/bitnami/

Another way is to copy files and folders under dokuwiki as root to /home/dokuwiki1/.local/share/containers/storage/volumes/dokuwiki-data/_data/ and set right owner/permissions afterwards.

Alternatively you could move the pages (not media) by using the Advanced plugin that provides an import/export utility.

EDIT:

I didn’t test the migration, maybe there’s an issue regarding the configuration files but saving the DokuWiki app settings in the cluster-admin should hopefully reconfigure everything and make it work again.

[danb35 (Dan)]

@mrmarkuz

Another way is to copy files and folders under dokuwiki as root to /home/dokuwiki1/.local/share/containers/storage/volumes/dokuwiki-data/_data/ and set right owner/permissions afterwards.

This did the trick, though I do kind of wonder what’s up with the owner of 1018504. But that’s easy enough to change with chown, and it seems to be up.

[dnutan (Marc)]

Just a general “For Our Information” note (although quotes are out of context they still provide some useful info):

@davidep

As said many times, fixing the ownership to the correct value is a real challenge in the containers world and for this reason absolute path operations must be avoided.

@davidep

Writing files into container volumes with such absolute paths is dangerous. It bypasses the uid:gid namespace and leads to access issues.

@davidep

Using absolute paths like this bypasses the user namespace applied by Podman: it is a dangerous approach.

@davidep

As always I suggest to avoid writing directly into system absolute paths with some “_data” path components, because it may have ownership and SELinux implications. The safe approach is to use Podman commands, like “podman exec”.

@davidep

When ownership is changed from a foreign user namespace, uid/gid numbers cannot be mapped and fall back to nobody/nogroup.

@davidep

Namespaces are important to understand the rich environment of containers, where service processes run: namespaces(7) - Linux manual page

Additionally:

@davidep

use podman unshare to edit the file with the host’s text editor as written above (Samba5 AD, DNS Nethserver8 - #2 by davidep), to preserve the correct file ownership and context.

man podman unshare

[danb35 (Dan)]

I’m generally familiar with Docker and host paths, but clearly NS8’s use of containers is different than what I’ve used elsewhere. Looks like more reading to do…

[Andy_Wismer (André Wismer)]

Hi @mrmarkuz

@mrmarkuz

/bitnami/dokuwiki.

I have docuwiki installed from the Software Center, but I can’t find any /bitnami folder.
I do have a folder /home/dokuwiki1

So: Do I need to create a top level folder bitnami first?

My 2 cents
Andy

[dnutan (Marc)]

It’s the data volume for dokuwiki, as seen from the podman container.

runagent -m dokuwiki1 podman exec -ti dokuwiki ls /bitnami/dokuwiki/

@Andy_Wismer

So: Do I need to create a top level folder bitnami first?

No.