question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG] Latest image - ENABLE_IPV6 not being honored?

See original GitHub issue

I’ve used this container for years now. Just this morning, I pulled the latest :alpine image and tried to start the container, and I get the following error:

ERROR: for proxy  Cannot start service proxy: driver failed programming external connectivity on endpoint nginx-proxy (xxx): Error starting userland proxy: listen tcp6 [::]:443: socket: address family not supported by protocol

I have ipv6 disabled on my system, and did not have the ENABLE_IPV6 environment variable set. I tried to set it to false to no avail. I also tried to use the :1586 image on docker hub, but I have the same issue.

I mount my configs in and none of them contain an ipv6 listener ([::]:443). Here’s the relevant docker-compose service:

proxy:
    image: nginxproxy/nginx-proxy:alpine
    labels:
      - "com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy=true"
    container_name: nginx-proxy
    environment:
      - ENABLE_IPV6=false
    ports:
      - 80:80
      - 443:443
    volumes:
      - ./client-sites/sites:/client-sites
      - ./proxy/conf.d:/etc/nginx/conf.d:rw
      - ./proxy/vhost.d:/etc/nginx/vhost.d:rw
      - ./proxy/html:/usr/share/nginx/html:rw
      - ./proxy/certs:/etc/nginx/certs:ro
      - /etc/localtime:/etc/localtime:ro
      - /var/run/docker.sock:/tmp/docker.sock:ro
    restart: unless-stopped

Listeners in my conf.d look like:

listen 443 ssl http2;

Thank you to the team for their hard work on this project! It has worked beautifully for many years, and I hope to have it working again soon 😃

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:8 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
buchdagcommented, Apr 13, 2021
0reactions
tnyeandersoncommented, Apr 13, 2021

@buchdag I think you’re right, it’s related to that issue. I will keep my eyes peeled on it… Thanks for the guidance! Gonna close this as it is not y’alls problem 😃

EDIT: Want to note that I am on 20.10.6, so it’s almost certainly that issue

Read more comments on GitHub >

github_iconTop Results From Across the Web

Docker 20.10.6: all containers stopped and cannot start if ipv6 ...
Our docker machines have ipv6 disabled in the kernel with the commandline ... [BUG] Latest image - ENABLE_IPV6 not being honored?
Read more >
Difficulty getting IPv6 working in a container
Containers are pihole:latest (the end goal) and debian:latest (as a sanity ... or if --ipv6 is being honored when the daemon is starting...
Read more >
538499 – IPv6-only network attachment fails, due to IPv4 ...
The major outstanding issues are: * Disconnecting an interface can leave IPv6 addresses/routes behind (see Bug 588149) * Link local IPv6 doesn't ...
Read more >
How to Fix an IPv6 No Network Access Error - Lifewire
Restart the device. · Restart the router and modem. · Update the device's operating system. · Check for network device driver updates (Windows)....
Read more >
Connectivity problems using IPv6 - Visual Studio Feedback
MicrosoftTeams-image (1).png. I solved the problem by disabling IPv6 on my Windows client where i am working on. Now i do not get...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found