[BUG] The newest arch-xfce cannot be started.

[silmarine]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I build a custom image from the arch-xfce image for my kasm server. The only customizations I make is installing additional apps. I've used the same docker file for a year with no issues until the most recently release. Now kasm throws the following error:

Exception creating Kasm: Traceback (most recent call last):
  File "docker/api/client.py", line 265, in _raise_for_status
  File "requests/models.py", line 1021, in raise_for_status
requests.exceptions.HTTPError: 409 Client Error: Conflict for url: http+docker://localhost/v1.47/exec/5e103779d9063ae3ba0b0eb6dce20ec0bf2be9055db9f2f76ed56de9ef26c8e3/start

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "__init__.py", line 574, in post
  File "provision.py", line 1990, in provision
  File "docker/models/containers.py", line 210, in exec_run
  File "docker/utils/decorators.py", line 19, in wrapped
  File "docker/api/exec_api.py", line 167, in exec_start
  File "docker/api/client.py", line 271, in _result
  File "docker/api/client.py", line 267, in _raise_for_status
  File "docker/errors.py", line 39, in create_api_error_from_http_exception
docker.errors.APIError: 409 Client Error for http+docker://localhost/v1.47/exec/5e103779d9063ae3ba0b0eb6dce20ec0bf2be9055db9f2f76ed56de9ef26c8e3/start: Conflict ("Container 03ffa743e5cd642b16c1a6b0ad3df5036d0dfe4ef78e1f7177631bab71972b6b is restarting, wait until the container is running")
Traceback (most recent call last):
  File "docker/api/client.py", line 265, in _raise_for_status
  File "requests/models.py", line 1021, in raise_for_status
requests.exceptions.HTTPError: 409 Client Error: Conflict for url: http+docker://localhost/v1.47/exec/5e103779d9063ae3ba0b0eb6dce20ec0bf2be9055db9f2f76ed56de9ef26c8e3/start

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "__init__.py", line 574, in post
  File "provision.py", line 1990, in provision
  File "docker/models/containers.py", line 210, in exec_run
  File "docker/utils/decorators.py", line 19, in wrapped
  File "docker/api/exec_api.py", line 167, in exec_start
  File "docker/api/client.py", line 271, in _result
  File "docker/api/client.py", line 267, in _raise_for_status
  File "docker/errors.py", line 39, in create_api_error_from_http_exception
docker.errors.APIError: 409 Client Error for http+docker://localhost/v1.47/exec/5e103779d9063ae3ba0b0eb6dce20ec0bf2be9055db9f2f76ed56de9ef26c8e3/start: Conflict ("Container 03ffa743e5cd642b16c1a6b0ad3df5036d0dfe4ef78e1f7177631bab71972b6b is restarting, wait until the container is running")

I added the uncustomized arch-xfce image from the linuxserver.io repository to test and it also gets the same error. I built the custom image with arch-xfce-2024-12-20-ls183 image and that one works fine. I've also tested some other tags, like debian-xfce, from the newest release and it worked fine so it seems to be an issue only with arch-xfce. Following is some more logs from running the docker container in terminal:
custom image with latest arch-xfce:

$ docker run --rm -it --shm-size=512m -p 6901:6901 -e VNC_PW=password arch:custom
/package/admin/s6-overlay/libexec/preinit: info: /run belongs to uid 0 instead of 1000 - fixing it
/run/s6/basedir/scripts/rc.init: line 26: /docker-mods: Permission denied
/run/s6/basedir/scripts/rc.init: warning: hook /docker-mods exited 126
[migrations] started
[migrations] no migrations found
groupmod: Permission denied.
groupmod: cannot lock /etc/group; try again later.
usermod: no changes
───────────────────────────────────────
  _____ __ __ _____ _____ _____ _____ 
 |     |  |  |   __|_   _|     |     |
 |   --|  |  |__   | | | |  |  | | | |
 |_____|_____|_____| |_| |_____|_|_|_|
       _____ __ __ _ __    ____  
      | __  |  |  | |  |  |    \ 
      | __ -|  |  | |  |__|  |  |
      |_____|_____|_|_____|____/ 

  Based on images from linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    911
User GID:    1000
───────────────────────────────────────
/etc/s6-overlay/s6-rc.d/init-adduser/run: line 35: /usr/sbin/lsiown: Permission denied
/etc/s6-overlay/s6-rc.d/init-adduser/run: line 36: /usr/sbin/lsiown: Permission denied
/etc/s6-overlay/s6-rc.d/init-adduser/run: line 37: /usr/sbin/lsiown: Permission denied
s6-rc: warning: unable to start service init-adduser: command exited 126

Expected Behavior

Kasm can launch the latest arch-xfce image.

Steps To Reproduce

Add the Arch XFCE workspace to Kasm and run it. I'm not sure if this is a problem specifically with working with kasm or if the issue also appears with running webtop:arch-xfce alone.

Environment

- OS: Debian 12
- How docker service was installed: via apt
- Docker version: 27.4.1, build b9d17ea
- Kasm Version: 1.16.0

CPU architecture

x86-64

Docker creation

Just using Kasm, I don't think there is anything interesting to screenshot that isn't already in the current behavior description.

Container logs

N/A