Dood to dind #201
Open
Dood to dind #201
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
joshrwolf
force-pushed
the
dood-to-dind
branch
2 times, most recently
from
dada544 to
b956f9c
Compare
joshrwolf
force-pushed
the
dood-to-dind
branch
from
b956f9c to
d136cab
Compare
1 task
jdolitsky
approved these changes
Oct 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
successor to #181.
this changes the docker harness to instead be a
dindvariant created dynamically with the bundler changes landed in #195.the docker harness is now a single container thats running its own docker daemon in the background, which ultimately makes the harness "feel" a lot more like a native host docker system, without all the footguns of
dood.additionally, this brings the harness entirely within
imagetest, meaning teardowns properly clean up any containers/networks/resources created within the harness