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

Unable to install packages within /bin/toolbox env: At least xMB more space needed on the / filesystem. #2889

Closed
ivanovaleksandar opened this issue Jun 11, 2018 · 4 comments
Labels
area/guest-vm General configuration issues with the minikube guest VM 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. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@ivanovaleksandar
Copy link

ivanovaleksandar commented Jun 11, 2018

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Environment:

Minikube version : v0.27.0

  • OS : MacOS High Sierra
  • VM Driver : virtualbox
  • ISO version : minikube-v0.26.0.iso

What happened:
When trying to install (whichever) package inside minikube even though there is enough space (the disk size when creating the box is ~30GB), it fails with:

Error Summary
-------------
Disk Requirements:
   At least xMB more space needed on the / filesystem.

What you expected to happen:
To install package as expected

How to reproduce it (as minimally and precisely as possible):

user $ minikube ssh
$ /bin/toolbox 

[root@minikube ~]# dnf install nano
Last metadata expiration check: 0:46:47 ago on Mon Jun 11 13:36:43 2018.
Dependencies resolved.
=======================================================================================================
 Package             Arch                  Version                        Repository              Size
=======================================================================================================
Installing:
 nano                x86_64                2.5.3-2.fc24                   updates                551 k

Transaction Summary
=======================================================================================================
Install  1 Package

Total download size: 551 k
Installed size: 2.1 M
Is this ok [y/N]: y
Downloading Packages:
nano-2.5.3-2.fc24.x86_64.rpm                                           561 kB/s | 551 kB     00:00
-------------------------------------------------------------------------------------------------------
Total                                                                  359 kB/s | 551 kB     00:01
Running transaction check
Transaction check succeeded.
Running transaction test
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Transaction check error:
  installing package nano-2.5.3-2.fc24.x86_64 needs 3MB on the / filesystem

Error Summary
-------------
Disk Requirements:
   At least 3MB more space needed on the / filesystem.

From Minikube CoreOS VM:

$ df -h
Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        928M     0  928M   0% /dev
tmpfs          1001M     0 1001M   0% /dev/shm
tmpfs          1001M   17M  984M   2% /run
tmpfs          1001M     0 1001M   0% /sys/fs/cgroup
tmpfs          1001M  8.0K 1001M   1% /tmp
/dev/sda1        25G  1.9G   22G   8% /mnt/sda1
/Users          234G   53G  182G  23% /Users
$ ls -la /var/lib/toolbox/
total 0
drwxr-xr-x  3 root root 0 Jun 11 14:26 .
drwxr-xr-x 17 root root 0 Jun 11 13:41 ..
drwxr-xr-x 18 root root 0 Jan  1  1970 docker-fedora-24

Within the created container with /bin/toolbox (in this case):

[root@minikube ~]# df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs          1001M     0 1001M   0% /tmp
tmpfs          1001M     0 1001M   0% /dev
tmpfs          1001M     0 1001M   0% /dev/shm
tmpfs          1001M  4.0K 1001M   1% /run
tmpfs          1001M   17M  984M   2% /media/root/run
devtmpfs        928M     0  928M   0% /media/root/dev
tmpfs          1001M     0 1001M   0% /media/root/dev/shm
tmpfs          1001M     0 1001M   0% /media/root/sys/fs/cgroup
tmpfs          1001M  8.0K 1001M   1% /media/root/tmp
/dev/sda1        25G  1.9G   22G   8% /media/root/mnt/sda1
overlay          25G  1.9G   22G   8% /media/root/var/lib/docker/overlay2/3a1052475a09324aff10e4a3ec234bc2e8bb9b7d0b87bfdfdd2d3058d2b2705f/merged
overlay          25G  1.9G   22G   8% /media/root/var/lib/docker/overlay2/4009399e28bcf3dc28af10c96e69c1305d82956cc366d68b4dbdae6cb163d028/merged
shm              64M     0   64M   0% /media/root/var/lib/docker/containers/c60b32897dcca5a4ebbdecd4e5586d0e3333864ea68781ef891cbe2a47dc3000/shm
overlay          25G  1.9G   22G   8% /media/root/var/lib/docker/overlay2/c80c6fbade2c8997f3819c979a4b1e8666072cdd06b0b3d7c526b025d94b0441/merged
shm              64M     0   64M   0% /media/root/var/lib/docker/containers/4927cc0e509edc62a130a435ca8335efea4edbc9c966bd85beab47af8c09bbb8/shm
overlay          25G  1.9G   22G   8% /media/root/var/lib/docker/overlay2/c29a6d1f34c58d714e202bbd88bffa27320b8f66535750abde49b660c7971019/merged
overlay          25G  1.9G   22G   8% /media/root/var/lib/docker/overlay2/7929b257b25187c74739213d08a9859cdefad63eb5cac3e8895f678189d73d7c/merged
shm              64M     0   64M   0% /media/root/var/lib/docker/containers/3486c4fdb1aa97803582e10d0fee60ab5bb0ef9cf77e0b5eecb85c4f01d1251a/shm
shm              64M     0   64M   0% /media/root/var/lib/docker/containers/d0089ae78d4e12694f681a36af825135b49ff401c15178e8c43dafed0b448123/shm
shm              64M     0   64M   0% /media/root/var/lib/docker/containers/527febac9d8bf096f86fd56bdc14d4a4a78a528356e2b77b628bae30a473a9e0/shm
overlay          25G  1.9G   22G   8% /media/root/var/lib/docker/overlay2/687105e12f042fc665fb83636f81279a75333a057692e2a3b021b96d9c2b2e2c/merged
overlay          25G  1.9G   22G   8% /media/root/var/lib/docker/overlay2/9b577660268c6211990761941f4364f19695e21f9e5a11e50605372606b35991/merged
overlay          25G  1.9G   22G   8% /media/root/var/lib/docker/overlay2/fb7dbfacb6a8a3ba0b1ab4b8e8cdf065e60f427f377f1c4442c055f07b91709c/merged
overlay          25G  1.9G   22G   8% /media/root/var/lib/docker/overlay2/b6cf4d6290dd0bd3c3ec99230559f41643de17dd266755f3f23f98a2d65bca5a/merged
tmpfs          1001M   12K 1001M   1% /media/root/var/lib/kubelet/pods/1cc5b646-6d7c-11e8-9206-0800277d7bc2/volumes/kubernetes.io~secret/kube-dns-token-r64tt
tmpfs          1001M   12K 1001M   1% /media/root/var/lib/kubelet/pods/1cc230f4-6d7c-11e8-9206-0800277d7bc2/volumes/kubernetes.io~secret/kube-proxy-token-6plm4
overlay          25G  1.9G   22G   8% /media/root/var/lib/docker/overlay2/df00ed30c75582a77f8e6cf9d7aa5baed4ebb4b0dadb8e362273a0abc8b81487/merged
shm              64M     0   64M   0% /media/root/var/lib/docker/containers/71afd3170e56202d94ef2d560fb595c57bf7070474008f03711b431eda229310/shm
overlay          25G  1.9G   22G   8% /media/root/var/lib/docker/overlay2/a5b8a443c3e7e0ded7e5d415f25def55467e4fb315af397324e006a139262d2f/merged
shm              64M     0   64M   0% /media/root/var/lib/docker/containers/55d5215a1e61c77e2d24c82efa9c49b3df2a1e26fe8ea5517a98396d1f7a9134/shm
overlay          25G  1.9G   22G   8% /media/root/var/lib/docker/overlay2/163ae2a853a49eb8f7032d76c782d22d3e565f8d30134e53bc64e90903ad75ce/merged
overlay          25G  1.9G   22G   8% /media/root/var/lib/docker/overlay2/9c00a4dd06c91bb3a9bc00f74b5a9d010578f350a638c0d538627c791459de2d/merged
tmpfs          1001M   12K 1001M   1% /media/root/var/lib/kubelet/pods/35300598-6d7c-11e8-9206-0800277d7bc2/volumes/kubernetes.io~secret/default-token-cvz22
overlay          25G  1.9G   22G   8% /media/root/var/lib/docker/overlay2/d53e586664026d60f45b1a951b8b93d95230095fff2e0ff84c6864c0cd486d93/merged
tmpfs          1001M   12K 1001M   1% /media/root/var/lib/kubelet/pods/3546e0e4-6d7c-11e8-9206-0800277d7bc2/volumes/kubernetes.io~secret/storage-provisioner-token-77r9w
shm              64M     0   64M   0% /media/root/var/lib/docker/containers/59ae2f28363fe100ae59d2836eea7e2a21f777930e42d65030441aca711e0b00/shm
overlay          25G  1.9G   22G   8% /media/root/var/lib/docker/overlay2/ace5a8815424300c6fef650d2b4ba34bb01c6b39e4643d12bc03b446396b8111/merged
shm              64M     0   64M   0% /media/root/var/lib/docker/containers/034f9a8793d933fbd57e2cb210cbfb762bdd2801b3c5a08101b069963596e294/shm
overlay          25G  1.9G   22G   8% /media/root/var/lib/docker/overlay2/f478d38639f5c1bce38c19775208d77134c84025d58897d52bce5f91a70a3899/merged
overlay          25G  1.9G   22G   8% /media/root/var/lib/docker/overlay2/7b84c024f8af0f6f7f04845cdc15a843a072e52ab29d5b4925488b6ccd890695/merged
overlay          25G  1.9G   22G   8% /media/root/var/lib/docker/overlay2/04e066dfea32198806886eefd3ba8bb5c39cd30dde0627fff1818ca968652839/merged
overlay          25G  1.9G   22G   8% /media/root/var/lib/docker/overlay2/785aaa835ec41c621d9b394ae9d04c88769d26ce53917b5e59202a6b96f7811f/merged
overlay          25G  1.9G   22G   8% /media/root/var/lib/docker/overlay2/97a83448c90b85c278a8f6e89d0c547831d82dc5aeefcd56f6c7c24fe0940259/merged
/Users          234G   53G  182G  23% /media/root/Users
tmpfs          1001M     0 1001M   0% /sys/fs/cgroup

Output of minikube logs (if applicable):
Nothing relevant in the logs

Anything else do we need to know:
If there is another way that a package can be installed, this will resolve the issue.

@lucamartinetti
Copy link

+1

@tstromberg tstromberg changed the title Using /bin/toolbox to install packages fails with: more space needed Unable to install packages within /bin/toolbox env: At least xMB more space needed on the / filesystem. Sep 19, 2018
@tstromberg tstromberg added kind/bug Categorizes issue or PR as related to a bug. area/guest-vm General configuration issues with the minikube guest VM labels Sep 19, 2018
@gdemarcsek
Copy link

+1

@marcindulak
Copy link

Same problem with minikube v0.30.0.

The toolbox is an old Fedora-24 #3058

@tstromberg
Copy link
Contributor

I happened to take another look at this today, and the fun part is that there is actually enough space (at least when launched from kvm2):

[root@minikube /]# dd if=/dev/zero bs=1024k count=300 of=/x
300+0 records in
300+0 records out
314572800 bytes (315 MB, 300 MiB) copied, 1.00873 s, 312 MB/s
[root@minikube /]# ls -lad /x
-rw-r--r-- 1 root root 314572800 Jan 24 16:29 /x
[root@minikube /]# du -h /x
300M	/x

I believe the issue here is that the container doesn't sees the disk as both 0 bytes large, and no space available:

[root@minikube ~]# df -h .
Filesystem      Size  Used Avail Use% Mounted on
rootfs             0     0     0    - /

Regardless, we should fix this soon. It's a drag having a feature that's effectively useless.

@tstromberg tstromberg added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. 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. labels Jan 24, 2019
@tstromberg tstromberg added this to the v1.0.0-candidate milestone Jan 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/guest-vm General configuration issues with the minikube guest VM 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. 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

No branches or pull requests

5 participants