-
Notifications
You must be signed in to change notification settings - Fork 437
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow overriding custom kamal
network
#1006
Comments
According to the upgrade guide, the recommendation for customizing the network is to use the |
then I would need to create a network called “kamal” with host access, which is far from ideal. i dont want all containers with host access, nor have to deal with port mapping because some containers port clash and host network exposes it all |
@djmb I can add a configuration option to change the network if you are okay with this. |
I don't think this would work - it would put the app and proxy containers in a host network as well, and then the proxy won't be able to access the app container by its container ID. @igor-alexandrov - yes please if you have a chance to add this 👍 We'd add something like accessories:
redis:
image: redis:latest
port: 6379
network: host |
you can have your accessories on multiple networks, for example for a Typesense cluster, static IPs are required. I solved this by adding:
this way the accessory is on the kamal network as well on my-custom-net |
|
hey 👋🏻
I'm running a couple of accessories that require host network mode and since v2, Kamnal forces the usage of custom
kamal
network.Is there any chance to make this option configurable? These containers do not run behind a proxy anyway so there's no need for them to be discoverable
The text was updated successfully, but these errors were encountered: