-
Notifications
You must be signed in to change notification settings - Fork 4.5k
connectors-ci: per connector dockerd #28566
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
Conversation
Before Merging a Connector Pull RequestWow! What a great pull request you have here! 🎉 To merge this PR, ensure the following has been done/considered for each connector added or updated:
If the checklist is complete, but the CI check is failing,
|
692b84e
to
a04352d
Compare
a04352d
to
5d0d282
Compare
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.
dockerd = context.dockerd_service | ||
docker_hostname = "global-docker-host" | ||
dockerd_service = with_dockerd_service(context) | ||
docker_hostname = f"{slugify(context.connector.technical_name)}-docker-host" |
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.
👍
Closing as unexpected Dagger / Docker errors were observed on the nightly build and #28000 is showing good progress. |
What
Closes #27867
#28000 is our best bet at reducing reliance on dockerd and its potential over caching issues. But it's currently blocked because I'm looking for advices from the Dagger team for the dagger-in-dagger usecase.
This PR is an alternative approach to try to increase isolation in CAT run:
We originally had one global docker daemon shared accross containers and we suspect it to be the root cause dubious connector command output in CAT causing transient CAT failures.
Having a per-connector dockerd was not the recommended approach by the Dagger team as it creates a lot of overhead and services to manage for the engine. But we're trying this approach again to see if the original issues we had persist / have been solved in the latest Dagger version.
Tests
A "nightly build" on all GA connectors is running here