docker-volumes | Docker Volume Manager | Continuous Deployment library

Docker Desktop for Mac runs dockerd in a Linux virtual machine.

A "volume" is created and stored by dockerd on the Linux virtual machine. The volume is not directly accessible from macos.

The /var/lib/docker/volumes/orthanc_docker_ris_MWL/_data path can be accessed by running a container in the VM's namespace:

But, how can I downgrade to an older version image, if the latest version does not work as expected or any problem comes? I found the docker tag concept and not sure how to apply it?

The easiest way would be to destroy the instance you were not happy with, start a new one (with v9.0.1) from scratch and restore the files/DB from your backup. I am assuming you made the backup before the upgrade.

image: kiwitcms/kiwi:9.0.1 works?

In theory that would work but in practice it won't because Kiwi TCMS upstream doesn't ship version tagged container images. See https://kiwitcms.org/#subscriptions, lines Only latest releases vs. Versioned releases from kiwitcms/version.

Or how should I tag version 9.0.1

Depending on what you've already done or not done this could either be possible or not possible:

• Execute docker images and if you see something like

You are getting errors because you don't understand what is happening. The commands and blog post referenced above are for backup & restore of the entire database, not selectively removing information which you don't want to be there anymore:

1. sqlflush will remove all information from all tables
2. migrate will create DB schema (which already exists) and initial records in some tables. Because the DB schema already exists and the internal Django reference to which migration has been applied last hasn't changed you get a "No migrations to apply" message
3. Because no migrations were applied some initial records aren't created. In this case a group with hard-coded name "Administrator".
4. refresh_permissions fails because it is looking for a group with the name "Administrator"

You can either:

1. Re-create all missing records by hand or
2. Create a clean installation of Kiwi TCMS and use that as your main instance or
3. Keep the POC instance and delete only the records you don't want - either one-by-one from the admin panel or using an ORM query via manage.py shell.

Something similar to this

I added this to my gitlab-ci.yml:

The Unix socket file /var/run/docker.sock is normally created by the Docker daemon. If you run something else as the main container process, the socket won't get created. You can directly look by running a container with a non-Docker main process, like /bin/ls:

You're not going to be able to run another docker container inside the container you created in Azure ACI. In order to achieve "docker-in-docker" (dind), the daemon instance (your ACI container in this case) needs to be running in privileged mode which would allow escalated access to the host machine that you are sharing with other ACI users. You can read about this more on Docker hub where it says:

Note: --privileged is required for Docker-in-Docker to function properly, but it should be used with care as it provides full access to the host environment, as explained in the relevant section of the Docker documentation.

The common solution for this is to use an auto-scale group of 0 or more VMs to provide compute resources to your gitlab runners and the containers they spawn.

• Gitlab docs - docker-machine autoscaler
• blog post re: doing this on Azure https://www.n0r1sk.com/post/on-premise-gitlab-with-autoscale-docker-machine-microsoft-azure-runners/

Change your copy line like this

You can start your container as root, allow the ENTRYPOINT script to perform any changes you want, and then switch to an unprivileged user when you execute the container CMD. E.g., use an ENTRYPOINT script something like this: