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
Currently docker makes an /etc/hosts file dynamically. So if there are any /etc/hosts settings on the host needed by a container, it will fail
Bad ideas
mount hosts:/etc/hosts on top of container:/etc/hosts. This will loose entries that belong there for a container, and will break in more complicated scenarios.
mount hosts:/etc/hosts into container:/etc/hosts2, and have an entrypoint concatenate the two. This will not work. /etc/hosts is read only, (and dynamic I think).
network mode = hosts. That's not segregated at ALL!
Ideas:
mount hosts:/etc/hosts into container:/etc/hosts2, and have an entrypoint concatenate the two.
Add the ability to Just-docker-compose to parse /etc/hosts, ignore localhost entries, and turn additional entries into extra_hosts entries.
Currently docker makes an /etc/hosts file dynamically. So if there are any /etc/hosts settings on the host needed by a container, it will fail
Bad ideas
mount hosts:/etc/hosts into container:/etc/hosts2, and have an entrypoint concatenate the two. This will not work. /etc/hosts is read only, (and dynamic I think).Ideas:
Just-docker-compose
to parse /etc/hosts, ignore localhost entries, and turn additional entries into extra_hosts entries.Related:
The text was updated successfully, but these errors were encountered: