-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
WIP: Attempt to Reenable TestInet{EndPoint,LayerDNS} for CI #500
WIP: Attempt to Reenable TestInet{EndPoint,LayerDNS} for CI #500
Conversation
Negative. TestInet{EndPoint,LayerDNS} still fail with Docker:
Though for Linux hosts on Travis CI, it looks like it should work if so configured with this: https://docs.docker.com/config/daemon/ipv6/. |
Trying 9dcd412 to see if that, at least, addresses the issue in the base Travis CI Linux container. There may still be more Docker configuration required. |
No go with that change. Will try something alone these lines. |
|
||
linux) | ||
# By default, Travis CI does not have IPv6 enabled on | ||
# Linux. Ensure that IPv6 is enabled since Weave, and its unit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Change Weave
to CHIP
If you please: ensure unrelated commits you've incorporated have already landed prior to this one landing? This looks blunderbuss-y. I recognize some of the work, but not all. |
Yes, this is a WIP PR and should have been a draft as an experiment to try to get IPv6 working in Docker on Travis. I'll mark it as such. |
5abde8e
to
6ccf92e
Compare
We are moving from Travis CI to Circle CI: https://circleci.com/docs/2.0/faq/#can-i-use-ipv6-in-my-tests |
…rt on Linux containers.
70f5913
to
c8166f3
Compare
Some possible clues here: https://github.com/prometheus/blackbox_exporter/blob/master/.circleci/config.yml |
@woody-apple, based on that example, I think the implication here is that the only way to use Docker is to manually launch Docker containers through the machine executor rather than launching them through the Docker executor. |
Yeah, once we get our plan upgraded tomorrow so it's not glacially slow, I'll take some stabs at this. Apologies for the delay. |
Here is another article on setting up IPv6 on docker (including minimum version requirements): And this article describes how to setup Docker in CircleCI within a NOTE: currently when you ssh into a fully sandboxed CircleCI docker, there is no It seems #803 is actually a working solution that resolves the issue using machine executor approach. |
@andy31415 @gerickson - is this OK to close, now that #1372 is in? |
Problem
TestInet{EndPoint,LayerDNS} needs IPv6 support and Docker on macOS does not support (and has not supported) IPv6.
Summary of Changes
However, now that we have stood up CI against Travis CI and/or GitHub actions with Docker on Linux instances, this may be mitigated and only an issue for local developers on macOS.
Trying moving TestInet{EndPoint,LayerDNS} from
noinst_PROGRAMS
back tocheck_PROGRAMS
.Fixes #323 and #329