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 mount fails for directories not belonging to current user #1822

Closed
NGTOne opened this issue Aug 14, 2017 · 4 comments
Closed

minikube mount fails for directories not belonging to current user #1822

NGTOne opened this issue Aug 14, 2017 · 4 comments
Labels
area/mount kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@NGTOne
Copy link

NGTOne commented Aug 14, 2017

Is this a BUG REPORT or FEATURE REQUEST?: BUG REPORT

Minikube version:
minikube version: v0.21.0

Environment:

  • OS: Ubuntu 16.04.2
  • VM Driver: virtualbox
  • ISO version: testing

What happened:

Mounting /home/sebastian/code into /home/docker/src on the minikube VM
This daemon process needs to stay alive for the mount to still be accessible...
ufs starting
ssh command error:
command : 
sudo mkdir -p /home/docker/src || true;
sudo mount -t 9p -o trans=tcp,port=34143,dfltuid=1001,dfltgid=1001,version=9p2000.u,msize=262144 192.168.99.1 /home/docker/src;
sudo chmod 775 /home/docker/src;
err     : exit status 1
output  : chmod: changing permissions of '/home/docker/src': Input/output error

What you expected to happen:
/home/sebastian/code gets mounted successfully into /home/docker/src on the minikube.

How to reproduce it:

chown -R www-data /home/sebastian/code
minikube mount /home/sebastian/code:/home/docker/src
@r2d4 r2d4 added area/mount kind/bug Categorizes issue or PR as related to a bug. labels Aug 15, 2017
@r2d4
Copy link
Contributor

r2d4 commented Aug 17, 2017

You'll need to run the minikube mount command as that user if you want to mount a folder owned by that user.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/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 Jan 3, 2018
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 8, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/mount kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

4 participants