-
Notifications
You must be signed in to change notification settings - Fork 6
Insulate container operations from Docker Desktop under WSL #66
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
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -8,6 +8,12 @@ export DEVTOOLS_DISTROBOX | |
| : "${DEVTOOLS_SYNC_DISTROBOX:=bar-sync}" | ||
| export DEVTOOLS_SYNC_DISTROBOX | ||
|
|
||
| # Our own Docker client config; Docker Desktop's ~/.docker/config.json names a | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Debated putting this in There's also a timing problem with That said, the This does add a minor risk if someone has DOCKER_CONFIG on their shell, but that's kind of expected/I'm fine with it — Docker Desktop itself doesn't set that var, it writes ~/.docker/config.json.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Seems fine given the use case, I have never heard of someone setting |
||
| # credsStore helper that can't be exec'd from WSL. | ||
| : "${DOCKER_CONFIG:=$DEVTOOLS_DIR/.devtools/docker}" | ||
| export DOCKER_CONFIG | ||
| mkdir -p "$DOCKER_CONFIG" | ||
|
|
||
| RED=$'\033[0;31m' | ||
| GREEN=$'\033[0;32m' | ||
| YELLOW=$'\033[1;33m' | ||
|
|
||
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.
From this comment.... should you just fix
build.shto pick podman first and fallback to docker if podman is unavailable?(I am aware from other discussion in this PR that podman still uses docker runtime in some cases)