nextcloud-spreed-signaling
nextcloud-spreed-signaling copied to clipboard
permission issue with docker compose up
nats-1 | nats-server: read /config/gnatsd.conf: is a directory
nats-1 | nats-server: read /config/gnatsd.conf: is a directory
nats-1 | nats-server: read /config/gnatsd.conf: is a directory
spreedbackend-1 | Preparing signaling server configuration in /config/server.conf ...
spreedbackend-1 | cp: can't create '/config/server.conf/server.conf.in': Permission denied
spreedbackend-1 | Preparing signaling server configuration in /config/server.conf ...
spreedbackend-1 | cp: can't create '/config/server.conf/server.conf.in': Permission denied
I got this issue when use sudo docker compose up
to start the container. How should I fix it?
- remove dirs docker/server.conf and docker/gnatsd.conf
- copy server.conf and gnatsd.conf into docker/
- remove dirs docker/server.conf and docker/gnatsd.conf
- copy server.conf and gnatsd.conf into docker/
I copy server.conf
and gnatsd.conf
(which are files) to docker/
The new error appears. It seems require gnatsd.conf
to be a folder.
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 "/home/aaron/nextcloud-spreed-signaling/docker/gnatsd.conf" to rootfs at "/config/gnatsd.conf": mount /home/aaron/nextcloud-spreed-signaling/docker/gnatsd.conf:/config/gnatsd.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
If I don't copy gnatsd.conf
to docker/
, docker compose up
will create a gnatsd.conf
dir. After that, error:
nats-1 | nats-server: read /config/gnatsd.conf: is a directory
Which OS / version of Docker is this? The steps described by @klatka should work fine, just tested this here myself.
Hello everyone,
I'm facing the same problem and have already tried everything possible. Every time if i start “docker compose up” a folder is created instead of a file. I am using Docker Compose version v2.29.1 on Ubuntu 22.04.4 LTS Have everyone an idea ?