No network attachment #4482
Bilge
started this conversation in
Feature Requests
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
For one of my service stacks, I want to use an external network. This works, however Coolify doesn't care, and still creates its own network to attach the containers to. This means containers are attached to both my network and Coolify's. Having containers attached to both makes it difficult to know which interface applications will use and thus difficult to create consistent security policy.
If I use a custom external network, it should either (automatically) not create its own, or there should simply be an option not to join a default network automatically.
Beta Was this translation helpful? Give feedback.
All reactions