Docker run for nextcloud fails

[Autchirion]

Hey Guys,

 

I'm posting this here, since it feels like an issue of the engine, rather than the container. I've got 2 nextcloud containers, one is nextcloud_prod, the other is nextcloud_test. This was working fine until recently, I changed some stuff, but reverted it back and now it's not working any more.

 

When I'm trying to start the container I get the message The command failed:

docker run
  -d
  --name='nextcloud_test'
  --net='swag'
  --cpuset-cpus='2,4,6,8,10,3,5,7,9,11'
  -e TZ="Europe/Berlin"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="server"
  -e HOST_CONTAINERNAME="nextcloud_test"
  -e 'PHP_MEMORY_LIMIT'='8192M'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://nextcloud.happyheppos.eu'
  -l net.unraid.docker.icon='https://decatec.de/wp-content/uploads/2017/08/nextcloud_logo.png'
  -p '3080:80/tcp'
  -v '/mnt/user/appdata/nextcloud_test/nextcloud':'/var/www/html':'rw'
  -v '/mnt/user/appdata/nextcloud_test/apps':'/var/www/html/custom_apps':'rw'
  -v '/mnt/user/appdata/nextcloud_test/config':'/var/www/html/config':'rw'
  -v '/mnt/user/nextcloud_data_prod':'/var/www/html/data':'rw'
  --user 99:100
  --sysctl net.ipv4.ip_unprivileged_port_start=0 'nextcloud:production' && docker exec
  -u 0 nextcloud_test /bin/sh
  -c 'echo "umask 000" >> /etc/apache2/envvars' && docker exec
  -u 0 nextcloud_test /bin/bash
  -c "apt update && apt install
  -y libmagickcore-6.q16-6-extra ffmpeg imagemagick ghostscript"
cab6b69a0570c5ce8417739b595a2a175f08e98ee01fca3a0fe37bceca09c7ad

The command failed.

 

Interestingly, this is basically only a copy/paste of the nextcloud_prod container which is working perfectly fine, the only thing I adapted is the container name for the Post arguments. Any ideas what might be going wrong here?

 

EDIT: I tried removing the && docker exec -u 0 nextcloud_test /bin/bash -c "apt update && apt install -y libmagickcore-6.q16-6-extra ffmpeg imagemagick ghostscript" from the post arguments and out of the sudden it's starting just fine and just calling the command manually (after the container is started without it) is also working like a charm.

 

Thank you in advance,

Autchi

Edited September 12, 2023 by Autchirion