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.
host.testcontainers.internal does not seem to work on ARM64 architecture
See original GitHub issueUsing test containers 1.16.3 and Ubuntu 20.04 on both arm64 and amd64 architectures.
I have a test which serves a file at localhost:3000/myfile, then inside a testcontainers docker container accesses it with curl http://host.testcontainers.internal:3000/myfile.
This all works fine for running on amd64 architectures, but when I run the same test on an ARM64 machine curl http://host.testcontainers.internal:3000/myfile returns nothing.
I checked on the arm machine that curl localhost:3000/myfile actually returns something, and it does.The problem is accessing that from the container.
Is this a bug or is the host.testcontainers.internal feature not supported on arm?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This is an interesting one - maybe going to be a puzzle for us to debug 😄
I’ve just tried running
ExposeHostTeston my M1 Mac with Docker Desktop (Server Version: 20.10.11) and it passed.I’ve also tried it against a (TCC) remote VM (which is 64-bit Ubuntu) and it worked too.
So I think that this isn’t specific to ARM, but some other combination of factors.
@eddumelendez updating to 1.17.5 fixes it for me. Thank you!