-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
toolbox: yum install fails: At least 47MB more space needed on the / filesystem. #3880
Comments
I believe the root cause here is how the filesystem shows up in the toolbox jail. Looking at https://redmine.ixsystems.com/issues/3668 - it may be possible to work around this by adding this to /etc/yum.conf:
Do you mind checking if that does the trick for you? If so, we just have to figure out how to get the toolbox updated to always include that - or of course, fix the underlying disk size plumbing issue. |
Thanks Thomas, you pointed me into the right direction! I added this line to /etc/dnf/dnf.conf: And it works fine now. |
That is a very good question, so far the answer has been Buildroot |
Today I played a bit with toolbox inside Minikube and everything worked like a charm so far (except that space problem mentioned above). So, the preferred way probably could be toolbox? |
We could hack this into This should probably check for both fedora and rootfs, before changing the DNF (yum 4) configuration. At least if we ever want to upstream the rootfs fix back to https://github.com/coreos/toolbox again Side note: with the "disk" space check disabled, it will probably kill the VM if you install something big. In minishift they "solved" this with a warning, and a: https://github.com/minishift/minishift-centos-iso/blob/master/scripts/yum-wrapper The better fix would be to symlink something over to the actual disk, I think they used that for /opt |
Linking the entire $ sudo mkdir /mnt/sda1/var/lib/toolbox
$ sudo ln -s /mnt/sda1/var/lib/toolbox /var/lib/toolbox
$ toolbox
Downloading sha256:01eb078129a [===============================] 90 MB / 90 MB
successfully removed aci for image: "sha512-319c511eb1e6ad373f65e9347a0157fe4f88e6e41d836ddd181aed24301e8f69"
rm: 1 image(s) successfully removed
Spawning container docker-fedora-29 on /mnt/sda1/var/lib/toolbox/docker-fedora-29.
Press ^] three times within 1s to kill container.
[root@minikube ~]# df -h /
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 17G 2.1G 14G 14% / Should also help the RAM situation, with toolbox installed. $ sudo du -hs /var/lib/toolbox/docker-fedora-29
288M /var/lib/toolbox/docker-fedora-29
|
Even a simple
So that's another 200M, without even installing any extra tools in the toolbox. |
I was trying to install additional packages into Minikube, but that seems not to work properly.
What is the preferred way to install additional tools in Minikube?
The exact command-lines used so that we can replicate the issue:
The full output of the command that failed:
Error Summary
Disk Requirements:
At least 47MB more space needed on the / filesystem.
But there is enough space available!
Which operating system version was used:
MacOSX Mojave
There is a closed ticket on this but I'm not sure whether it was fixed or dropped:
#2889
If dropped, as a developer tool it would be very handy to support to install additional tools inside Minikube and re-enable such a feature. This would simplify things a lot in our development cycles.
BTW: Thanks for your great work!
The text was updated successfully, but these errors were encountered: