Skip to content
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

Exposing hyperkit ip address for network=host setting #280

Open
bvkin opened this issue Mar 25, 2020 · 0 comments
Open

Exposing hyperkit ip address for network=host setting #280

bvkin opened this issue Mar 25, 2020 · 0 comments

Comments

@bvkin
Copy link

bvkin commented Mar 25, 2020

docker engine version: 19.03.8
docker desktop version: 2.2.0.4
hyperkit version: v0.20190802-4-g97f091

I am trying to run several containers inside of aws fargate task for an application I'm developing. All containers using the fargate service share a network interface, so to replicate this configuration locally I'm trying to use a docker-compose file where my containers are set to use the network=host option.

The containers are able to run as expected but I am not able to access any of the network services they provide. I'm guessing this is because they are sharing a network namespace with the docker engine's hyperkit vm rather than one with my mac computer.

I believe I can query for the hyperkit vm ip with the following command $ docker run --network host alpine ifconfig eth0. However, I still can't access the services using ports against this ip nor can I reach it using the ping command. Is there any way expose this ip when using network=host mode?

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant