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 image build path handling issue in Windows #15007

Closed
mattilaiatostek opened this issue Sep 23, 2022 · 3 comments · Fixed by #15074
Closed

minikube image build path handling issue in Windows #15007

mattilaiatostek opened this issue Sep 23, 2022 · 3 comments · Fixed by #15074
Assignees
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. os/windows priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.

Comments

@mattilaiatostek
Copy link

mattilaiatostek commented Sep 23, 2022

What Happened?

  • v1.27.0 minikube-windows-amd64.exe
  • Root of the project contains .dockerignore file with a line **/Dockerfile*
  • minikube image build -t myproject:latest -f subfolder/Dockerfile .
    --> C:\Users\user\AppData\Local\Temp\build.xxxxxxxxxx.tar is missing subfolder\Dockerfile and the build obviously fails within Minikube VM due to missing Dockerfile
  • minikube image build -t myproject:latest -f subfolder\Dockerfile .
    --> C:\Users\user\AppData\Local\Temp\build.xxxxxxxxxx.tar contains subfolder\Dockerfile, but the build obviously fails within Minikube VM because subfolder\Dockerfile is not a valid Linux path
  • Workaround: remove .dockerignore and use path subfolder/Dockerfile

Attach the log file

Operating System

Windows 10 Pro

Driver

Docker Desktop v4.12.0

@afbjorklund
Copy link
Collaborator

The path needs to be translated, from the DOS path on the host to the Unix path in the VM.

@afbjorklund afbjorklund added kind/bug Categorizes issue or PR as related to a bug. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. os/windows labels Sep 28, 2022
@ComradeProgrammer
Copy link
Member

ComradeProgrammer commented Oct 5, 2022

Can I have a try on this issue?
/assign ComradeProgrammer

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle stale
  • Close this PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. os/windows priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants