eGroupware watchtower

[thorsten]

Hallo Zusammen,

ich bekomme nach einem Update folgenden Fehler:

ERROR: for egroupware-watchtower Cannot start service watchtower: OCI runtime create failed: container_linux.go:345: starting container process caused “process_linux.go:430: container init caused “rootfs_linux.go:58: mounting \”/root/.docker/config.json\” to rootfs \"/var/lib/docker/overlay2/ec896d778cacc2207ad6f62a9655af86786e776aa9d7abeba494a73b99333196/merged\" at \"/var/lib/docker/overlay2/ec896d778cacc2207ad6f62a9655af86786e776aa9d7abeba494a73b99333196/merged/config.json\" caused \“not a directory\”"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

ERROR: for watchtower Cannot start service watchtower: OCI runtime create failed: container_linux.go:345: starting container process caused “process_linux.go:430: container init caused “rootfs_linux.go:58: mounting \”/root/.docker/config.json\” to rootfs \"/var/lib/docker/overlay2/ec896d778cacc2207ad6f62a9655af86786e776aa9d7abeba494a73b99333196/merged\" at \"/var/lib/docker/overlay2/ec896d778cacc2207ad6f62a9655af86786e776aa9d7abeba494a73b99333196/merged/config.json\" caused \“not a directory\”"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
ERROR: Encountered errors while bringing up the project.
dpkg: Fehler beim Bearbeiten des Paketes egroupware-docker (–configure):
installed egroupware-docker package post-installation script subprocess returned error exit status 1
Fehler traten auf beim Bearbeiten von:
egroupware-docker
E: Sub-process /usr/bin/dpkg returned an error code (1)

Was tun?

Grüße
Thorsten

[RalfBecker]

Der Fehler ist in den Paketen inzwischen behoben, führe einfach folgende Kommandos aus:

cd /etc/egroupware-docker
docker-compose stop watchtower
docker-compose rm -f watchtower
test -d /root/.docker/config.json && rmdir ©
test -f /root/.docker/config.json || echo "{}" > /root/.docker/config.json
docker-compose up -d

Das nicht vorhandene .docker/config.json (weil nie ein docker login gemacht) führte dazu das Docker statt dessen ein Verzeichnis angelegt hat.

Ralf

[thorsten]

Hi Ralf,

many thanks… läuft wieder!!

Grüße
Thorsten