-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
docker-env
errors if ~/.ssh
doesn't exist
#16933
Comments
Fix proposed in #16934 |
@sethrylan thank you for creating this issue, that is a regression and we must fix that, however it doesnt seem to be affecting the functionality of docker-env but scares the user with an ugly error message. |
docker-env
fails if ~/.ssh
doesn't existdocker-env
errors if ~/.ssh
doesn't exist
i confirm the same error happened to me (just today) - the workaround mkdir -p .ssh worked but this is a regression since it's causing 'Run on Cloud Run Emulator' to fail. cloud-code/installer/google-cloud-sdk/bin/minikube docker-env --shell none -p cloud-run-dev-internal --user=skaffold |
Hi @TenzinChang do you mind pinging me internally ? |
What Happened?
Starting with
v1.31.0
,docker-env
will fail if the~/.ssh
directory doesn't exist. This is the case on most linux hosts that have not generated ssh keys (e.g., short-lived VMs).Introduced in #15452.
The workaround is to run
mkdir -p ~/.ssh
.Attach the log file
log.txt
Operating System
Ubuntu
Driver
Docker
The text was updated successfully, but these errors were encountered: