February 15, 20251 yr Hey there, I've encountered problems with installing the LMS docker from CA. I've also tried a different container, which also had the same error (message below). The error appears on two seperate servers, so I don't think it's hardware related. As the error mentions the resolve.conf and I had to change my router last week I assume it has something to do with this. But checking the network settings everything seems to be OK. Any ideas? Diagnostics from both systems attached docker run -d --name='lms' --net='bridge' --pids-limit 2048 -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e HOST_HOSTNAME="LA-TV" -e HOST_CONTAINERNAME="lms" -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:5082]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/JPDVM2014/icons/main/lms.webp' -p '5082:5082/tcp' -v '/mnt/user/media/Musik/':'/music':'ro' -v '/mnt/user/appdata/lms':'/var/lms':'rw' -v '/mnt/user/appdata/lms/config/':'/etc/':'ro' --user 99:100 'epoupon/lms:latest' 8197c08cca88c8be68c8e9ecc80d2b4685cb03a8d7596a377600fa8811c8c405 docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/var/lib/docker/containers/8197c08cca88c8be68c8e9ecc80d2b4685cb03a8d7596a377600fa8811c8c405/resolv.conf" to rootfs at "/etc/resolv.conf": open /var/lib/docker/btrfs/subvolumes/4a1ff5d7f526765f5e254db6370c565eb7e46817854188dc23304cd7c854b0fe/etc/resolv.conf: read-only file system: unknown. Der Befehl ist fehlgeschlagen. la-nas-diagnostics-20250215-1403.zip la-tv-diagnostics-20250215-1402.zip
February 15, 20251 yr Community Expert You have a lot of GPFs and segfaults in log for la-nas. Have you done memtest recently?
February 15, 20251 yr Author No, I haven't due to the system being rock solid until these problems. I will run a memtest this weekend, so thanks. But I don't think that's related to the error during the container start.
February 15, 20251 yr Community Expert Solution Remove the mapping that is pointing to /etc. thats fucking it up this one -v '/mnt/user/appdata/lms/config/':'/etc/':'ro' I have no clue for what its needed BUT if its important, change the read-only to read-write -v '/mnt/user/appdata/lms/config/':'/etc/':'rw' Edited February 15, 20251 yr by Mainfrezzer
February 15, 20251 yr Author That did it, thanks a lot. That volume mapping is actually part of the template, but I haven't seen anything about it in the support thread... Strange.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.