Skip to content
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

sudo -E minikube image build breaks users ability to use docker build on none driver #16393

Closed
spowelljr opened this issue Apr 27, 2023 · 1 comment · Fixed by #16408
Closed
Assignees
Labels
area/image Issues/PRs related to the minikube image subcommand co/none-driver co/runtime/docker Issues specific to a docker runtime kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@spowelljr
Copy link
Member

Related #16386

The issue I'm running into is with Docker 23, they're deprecating the legacy builder builtin to Docker and want you to also install docker-buildx-plugin.

After implementing #16386, I'm running into a problem when I'm running sudo -E minikube image build as the buildx-plugin creates the file /home/<user>/.docker/buildx/activity/default after a build, but because of sudo -E it has root:root permissions. Then if I try to do a normal docker build after running the above it fails with ERROR: open /home/<user>/.docker/buildx/activity/default: permission denied.

So after running sudo -E minikube image build it essentially breaks the users ability to use docker build unless they change the permissions of /home/<user>/.docker/buildx/activity/default off of root:root.

@spowelljr spowelljr added kind/bug Categorizes issue or PR as related to a bug. co/none-driver priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Apr 27, 2023
@spowelljr spowelljr added this to the 1.31.0 milestone Apr 27, 2023
@spowelljr spowelljr added the area/image Issues/PRs related to the minikube image subcommand label Apr 27, 2023
@spowelljr
Copy link
Member Author

spowelljr commented Apr 27, 2023

If you start minikube with sudo minikube start and build with sudo minikube image build it works fine as it writes to /root/.docker/buildx/activity/default instead. But our documentation tells users to use sudo -E minikube.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/image Issues/PRs related to the minikube image subcommand co/none-driver co/runtime/docker Issues specific to a docker runtime kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant