Egroupware-docker (19.1.20191119) install error

[gjpc]

Despite the announcement that 19.1.20191119 was a Docker update, apt had an update of the entire egroupware-docker package. I hand updated the package as per earlier suggestions and witnessed the following errors:

Starting egroupware-watchtower ... error

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/02a5c6a6ed97ff1bcc31d0fe3387ca036238ed798af0aab998115aa2ce4bf132/merged\\\" at \\\"/var/lib/docker/overlay2/02a5c6a6ed97ff1bcc31d0fe3387ca036238ed798af0aab998115aa2ce4bf132/merged/config.json\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directorRecreating egroupware ... done
Recreating egroupware-nginx ...
Recreating egroupware-nginx ... done

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/02a5c6a6ed97ff1bcc31d0fe3387ca036238ed798af0aab998115aa2ce4bf132/merged\\\" at \\\"/var/lib/docker/overlay2/02a5c6a6ed97ff1bcc31d0fe3387ca036238ed798af0aab998115aa2ce4bf132/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.
Module proxy already enabled
Considering dependency proxy for proxy_http:
Module proxy already enabled
Module proxy_http already enabled
Considering dependency proxy for proxy_wstunnel:
Module proxy already enabled
Module proxy_wstunnel already enabled
Module headers already enabled

Egroupware started and works normally so far after the error.

[StefanU]

Hi gjpc,

this is a new package from today. This has nothing to do with the EGroupware container update. I’ll write more tomorrow.
I can’t say anything about the error messages. @RalfBecker has to look at that.

Stefan

[StefanU]

My Update:

Witout errors.

Stefan

[gjpc]

Do you have Rocket & Collabora installed? I don’t.

[StefanU]

Yes, of course I do. Especially Collabora I use.

However, this certainly has nothing to do with the error messages.

Stefan

[RalfBecker]

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/02a5c6a6ed97ff1bcc31d0fe3387ca036238ed798af0aab998115aa2ce4bf132/merged\" at \"/var/lib/docker/overlay2/02a5c6a6ed97ff1bcc31d0fe3387ca036238ed798af0aab998115aa2ce4bf132/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

The most important part is the very end: Are you trying to mount a directory onto a file

Problem is fixed with newer installation, but older ones experiencing this need to run the following commands:

cd /etc/egroupware-docker
docker-compose stop watchtower
docker-compose rm -f watchtower
rm -rf /root/.docker/config.json
echo "{}" > /root/.docker/config.json
docker-compose up -d

What does that do?

It deletes the directory Docker created, as you had no config.json file. Then it creates an empty one and starts everything up again.

Ralf

[gjpc]

cd /etc/egroupware-docker
docker-compose stop watchtower
docker-compose rm -f watchtower
rm -rf /root/.docker/config.json
echo “{}” > /root/.docker/config.jsondocker-compose up -d

Thanks Ralf. No errors on these commands. I guess this means that I won’t have to reboot the system on the next egroupware docker auto update like I did on the last one. The watchtower process is running now and egroupware comes up on system boot.

I’ll mark topic solved after the next docker auto update succeeds.