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
When i try to start the stack with portainer via repository i get the following error:
Container internet-speed-monitor-speedtester-1 Started
Error response from daemon: OCI runtime create failed: container_linux.go:367: starting container process caused: process_linux.go:495:
container init caused: rootfs_linux.go:60: mounting "/data/compose/21/telegraf/telegraf.conf" to rootfs at "/var/lib/docker/overlay2/17ac96b8523ba2911532177a13c052635cb5b03b825d1a02c07aade1db8b59eb/merged/etc/telegraf/telegraf.conf"
caused: 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
Is there is difference in using portainer or running it by hand? I am not very familiar with compose. I know basic docker.
The text was updated successfully, but these errors were encountered:
Mmmh, it seems that required files cannot be found (e.g. telegraf/telegraf.conf). How do you add the container/image to portainer? Do you use portainer locally (inside a docker container)?
I use the web interface of portainer to create a stack. Portainer supports
stack creation with git repositories. So I paste the url and the location
of the compose file. That's all.
Yes portainer itself is listed as container and therefore runs in docker.
Raimund ***@***.***> schrieb am Fr., 27. Jan. 2023, 19:47:
When i try to start the stack with portainer via repository i get the following error:
Is there is difference in using portainer or running it by hand? I am not very familiar with compose. I know basic docker.
The text was updated successfully, but these errors were encountered: