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 first testing, I had /var/run/docker.sock in the volumes, but swiftwave doesn't like that ( "stack configuration is not valid. only named volumes are supported.").
So I switched to docker_proxy_config (like your portainer example).
I'm assuming this should mount docker.sock like a normal docker-compose file:
volumes:
# mount the docker socket to allow to run docker containers from within the workers
- /var/run/docker.sock:/var/run/docker.sock
This is not working in my workers. If I under them there is no /var/run/docker.sock or any in the mount print out.
Also, this is what I see in my swiftwave dashboard for the workers:
Are you working on this issue?
No
The text was updated successfully, but these errors were encountered:
Describe the bug
Here is my template I'm attempting to use: https://gist.github.com/that0n3guy/61d6ca0d3c07f9a36089deb37837a37f
When first testing, I had /var/run/docker.sock in the volumes, but swiftwave doesn't like that ( "stack configuration is not valid. only named volumes are supported.").
So I switched to docker_proxy_config (like your portainer example).
I'm assuming this should mount docker.sock like a normal docker-compose file:
This is not working in my workers. If I under them there is no /var/run/docker.sock or any in the
mount
print out.Also, this is what I see in my swiftwave dashboard for the workers:
Are you working on this issue?
No
The text was updated successfully, but these errors were encountered: