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

network host binds to ipv6 not ipv4 #12

Open
phi0x opened this issue Sep 27, 2023 · 1 comment
Open

network host binds to ipv6 not ipv4 #12

phi0x opened this issue Sep 27, 2023 · 1 comment

Comments

@phi0x
Copy link

phi0x commented Sep 27, 2023

For some reason my container is binding to ipv6 instead of ipv4. Not sure why it's choosing to do that but it only occurs on containers which use 'host' (like this one, which is the only container I have running that uses 'host'). I used netstat -anp to find that it is bound to tcp6.

  --name=frontend-rwsols \
  --network="host" \
  -e APACHE2_PORT=9090 \
  -e PASSPHRASE="MyPass" \
  -e RWSOLS_COMPUTER_NAME="PC1","Editor PC" \
  -e RWSOLS_COMPUTER_MAC="11:C4:7B:6E:75:77","95:DE:81:C8:06:D9" \
  -e RWSOLS_COMPUTER_IP="192.168.3.183","192.168.3.219" \
  --restart unless-stopped \
  ex0nuss/remote-wake-sleep-on-lan-docker

netstat -anp

tcp6       0      0 :::9090                 :::*                    LISTEN      1862338/apache2

can't figure out how to make it bind to ipv4.

@phi0x
Copy link
Author

phi0x commented Sep 27, 2023

I ended up disabling ipv6 on my server as I don't use it anyways. That resolved the issue and is binding to ipv4 now. Not going to be ideal for some other users potentially but this is good enough for myself.

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