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

minikube requires docker upgrade to v19.03+ to address issues with chown on COPY #5913

Closed
harsimranmaan opened this issue Nov 14, 2019 · 5 comments · Fixed by #5914
Closed
Labels
co/runtime/docker Issues specific to a docker runtime kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@harsimranmaan
Copy link
Contributor

The exact command to reproduce the issue:
Have a docker file with
COPY --chown=${USER}:${GROUP} FILENAME .

docker build fails within minikube context.
The full output of the command that failed:
unable to convert uid/gid chown string to host mapping: can't find uid for user ${USER}: no such user: ${USER}

The output of the minikube logs command:
docker info | grep "Server Version"
Server Version: 18.09.9
which does not have the docker fix

The operating system version: macOS 10.14.6

Relates moby/moby#35018

harsimranmaan added a commit to harsimranmaan/minikube that referenced this issue Nov 14, 2019
@afbjorklund
Copy link
Collaborator

Probably want to use uid/gid meanwhile, or add the user to the container image proper

@harsimranmaan
Copy link
Contributor Author

The user is already part of the container image.

@afbjorklund
Copy link
Collaborator

Think that I misunderstood, the problem is not uid vs name - the problem is using environment variables in a (mostly static) Dockerfile. The output above is the actual error message and not something censored...

@afbjorklund
Copy link
Collaborator

Anyway, as I wrote in the PR we can upgrade Docker daemon but I want do it with the new k8s 1.17 and we should upgrade runc/containerd at the same time (as bundled with it)

@harsimranmaan
Copy link
Contributor Author

Let me know if you'd like me to update the PR with new components. I think the tests might be a bit brittle as they have been failing for same reasons on different PRs. Is this something I should worry about?

@afbjorklund afbjorklund added co/runtime/docker Issues specific to a docker runtime kind/feature Categorizes issue or PR as related to a new feature. labels Nov 15, 2019
@tstromberg tstromberg added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Nov 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/runtime/docker Issues specific to a docker runtime kind/feature Categorizes issue or PR as related to a new feature. 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.

3 participants