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
Bug [26.0.1, build d260a54] - Cannot access service #5014
Comments
This issue is not exclusive to @osinnowo as the problem hit me as well. I downgraded docker to the latest 25.0 release and all is well. |
Same here, I am having network issues accessing the containers after the upgrade to Docker version 26.0.1, build d260a54 on Ubuntu 22.04.4. I can provide additional information if needed. Thanks, |
Hi all - thank you for reporting. We'll need some more info to understand whether you're all seeing the same issue, and where the problem or problems are. @osinnowo ... in the nginx example:
@tkimball83, @mdima - similar questions ... what does your environment look like, what commands are you using? Are you using IPv4 like @osinnowo, or IPv6 like @thomascrha? If you can share logs or other diagnostic info, that might help. @thomascrha ... can you share any info about the IPv6 routing issues? How have you configured IPv6, what works from where etc? (Info as above, including |
Hello @robmry , Thanks, |
Thanks @mdima - early versions of 25.0.x had an issue with containers getting duplicate MAC addresses, which caused intermittent connectivity - although I'd have expected that to cause problems in 25.0.x too. It might be worth checking Just to double-check, the failures are intermittent over the lifetime of a single container? (It's not that intermittently newly instantiated containers don't work?) When there's an outage, and containers aren't accessible from the LAN - are they accessible from the docker host that's running them? Which sort of networking are you using, are the containers on a custom bridge network (as they would be in the original post's compose/nginx example)? If you're running multiple containers(?), do they all see the outage at the same time? Which version did you upgrade to 26.0.1 from? Did you try reverting to a 25.0.x version, and did that help? What sort of frequency/duration do the outages have? (If it works for a few seconds then fails for a few, that should be a bit easier to track down than a short failure in a long time.) If possible, it'd be good to capture the output of the commands I mentioned above when it's working and when it's broken for comparison. |
Dear @robmry , yes, you're right. I inspected my containers and I found two MAC collisions (involving 4 containers in total). Thanks, |
Ah, great! Thank you for the update, hopefully that'll have solved the problem in your case. |
Description
I upgraded to the latest build (Docker version 26.0.1, build d260a54) and when I run docker compose up, everything looks fine, service(s) is up, but I can't access these service over the browser or any other means. On the browser, it keeps loading for a long time and then finally stop, it seems as though request isn't hitting docker engine.
Reproduce
See sample docker-compose.yml:
When docker compose up is ran, it setup the service successfully with no crash but then the webserver service would be unreachable, this is also applicable my current project that have been running on docker for quite a while now, stopped just until now.
Any thought why this is happening?
Expected behavior
No response
docker version
Client: Docker Engine - Community Version: 26.0.1 API version: 1.45 Go version: go1.21.9 Git commit: d260a54 Built: Thu Apr 11 10:53:25 2024 OS/Arch: linux/amd64 Context: default Server: Docker Engine - Community Engine: Version: 26.0.1 API version: 1.45 (minimum version 1.24) Go version: go1.21.9 Git commit: 60b9add Built: Thu Apr 11 10:53:25 2024 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.31 GitCommit: e377cd56a71523140ca6ae87e30244719194a521 runc: Version: 1.1.12 GitCommit: v1.1.12-0-g51d5e94 docker-init: Version: 0.19.0 GitCommit: de40ad0
docker info
Additional Info
No response
The text was updated successfully, but these errors were encountered: