You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm getting the following error when trying to deploy the docker container both standalone with docker compose up and withing Portainer. I suspect it has to do with the files being directly linked in the volumes area, but trying to create them manually and add them later (as directories, or as files) only resulted in non-working setups.
Here's my docker-compose file, the other two files (mopidy.conf, snapserver.conf) were created with default config in their respective directories.
I changed the branch to master, container names and music directory just in case but nothing worked.
[redacted]@[redacted]:/mnt/docker/containers/music-server$ sudo docker compose up
[+] Running 2/0
✔ Container irissssssss Created 0.1s
✔ Container snapppppserver Created 0.0s
Attaching to irissssssss, snapppppserver
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 "/mnt/docker/containers/music-server/docker/mopidy/mopidy.conf" to rootfs at "/config/mopidy.conf": mount /mnt/docker/containers/music-server/docker/mopidy/mopidy.conf:/config/mopidy.conf (via /proc/self/fd/6), flags: 0x5000: 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 text was updated successfully, but these errors were encountered:
I've successfully got it working by first creating both the folders and files and attaching them as folders with the proper file contents (server.json, mopidy.conf & snapserver.conf), the contents of server.json I just copy pasted the ones of snapserver.conf.
Note that even this setup might work, it requires extra setup on the end user and potentially introduces a security risk (or at least unnecessary file exposure) by exposing such folder's content. It also prevents the automatic deployment with just the use of docker.
Iris version
:latest :master
Operating system(s) affected
Browser(s) affected
What happened?
I'm getting the following error when trying to deploy the docker container both standalone with
docker compose up
and withing Portainer. I suspect it has to do with the files being directly linked in thevolumes
area, but trying to create them manually and add them later (as directories, or as files) only resulted in non-working setups.Here's my docker-compose file, the other two files (mopidy.conf, snapserver.conf) were created with default config in their respective directories.
I changed the branch to master, container names and music directory just in case but nothing worked.
Logs
The text was updated successfully, but these errors were encountered: