[Bug] Startup Failes on 10-init-users.sh
zottelchin opened this issue · comments
Current Behavior
When starting the container, it fails on 10-init-users.sh and stops startup. I dug into the error and when changing the commands from sed-patch to sed i started up fine. I would like to contribute this via a PR but could not identify the file in this repo.
Expected Behavior
No response
Steps To Reproduce
No response
Environment
- OS: Debian
- OS version: bookworm
- CPU: Intel(R) Celeron(R) CPU N3450
- Docker version: Docker version 25.0.3, build 4debf41
- Device model:
- Browser/OS:
Container creation
Tried this with docker compose (copy from readme) and docker run (also from readme). To reproduce, docker run jlesage/makemkv is enough.
Container log
[init ] container is starting...
[cont-env ] loading container environment variables...
[cont-env ] APP_NAME: loading...
[cont-env ] APP_VERSION: loading...
[cont-env ] DISPLAY: executing...
[cont-env ] DISPLAY: terminated successfully.
[cont-env ] DISPLAY: loading...
[cont-env ] DOCKER_IMAGE_PLATFORM: loading...
[cont-env ] DOCKER_IMAGE_VERSION: loading...
[cont-env ] GTK2_RC_FILES: executing...
[cont-env ] GTK2_RC_FILES: terminated successfully.
[cont-env ] GTK2_RC_FILES: loading...
[cont-env ] GTK_THEME: executing...
[cont-env ] GTK_THEME: terminated successfully.
[cont-env ] GTK_THEME: loading...
[cont-env ] HOME: loading...
[cont-env ] QT_STYLE_OVERRIDE: executing...
[cont-env ] QT_STYLE_OVERRIDE: terminated successfully.
[cont-env ] QT_STYLE_OVERRIDE: loading...
[cont-env ] SUP_GROUP_IDS_INTERNAL: executing...
[cont-env ] SUP_GROUP_IDS_INTERNAL: terminated successfully.
[cont-env ] SUP_GROUP_IDS_INTERNAL: loading...
[cont-env ] TAKE_CONFIG_OWNERSHIP: loading...
[cont-env ] XDG_CACHE_HOME: loading...
[cont-env ] XDG_CONFIG_HOME: loading...
[cont-env ] XDG_DATA_HOME: loading...
[cont-env ] XDG_RUNTIME_DIR: loading...
[cont-env ] XDG_STATE_HOME: loading...
[cont-env ] container environment variables initialized.
[cont-secrets] loading container secrets...
[cont-secrets] container secrets loaded.
[cont-init ] executing container initialization scripts...
[cont-init ] 10-certs.sh: executing...
[cont-init ] 10-certs.sh: terminated successfully.
[cont-init ] 10-check-app-niceness.sh: executing...
[cont-init ] 10-check-app-niceness.sh: terminated successfully.
[cont-init ] 10-clean-logmonitor-states.sh: executing...
[cont-init ] 10-clean-logmonitor-states.sh: terminated successfully.
[cont-init ] 10-clean-tmp-dir.sh: executing...
[cont-init ] 10-clean-tmp-dir.sh: terminated successfully.
[cont-init ] 10-fontconfig-cache-dir.sh: executing...
[cont-init ] 10-fontconfig-cache-dir.sh: terminated successfully.
[cont-init ] 10-init-users.sh: executing...
[cont-init ] 10-init-users.sh: sed: cannot rename /etc/group: Invalid argument
[cont-init ] 10-init-users.sh: terminated with error 4.
Container inspect
No response
Anything else?
No response
Is the docker storage on a ZFS drive ?
yes, it is.
Ok, this scenario is not fully supported by ZFS (to be verified if it's still the case with the latest version).
Here are some links to existing issues where you can find more details and workarounds:
jlesage/docker-handbrake#286 (comment)
jlesage/docker-jdownloader-2#165
jlesage/docker-jdownloader-2#137
oh thanks 👍🏻