-
Notifications
You must be signed in to change notification settings - Fork 232
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
podman build: rootless build takes up a lot of disk space #1570
Comments
Can you test this with podman 4.4.4? Or better podman v4.5-rc2 or main branch. |
I'd rather use distro packages, so that I can easily upgrade and downgrade the components, and deps are correct. Ubuntu Btw. what changes there are to storage, and in which version? Only comment referring to "storage" in the release notes after v3.4.1, is this one for v4.5.0-rc2:
|
Note that it's very easy to test this bug. Just make sure fuse-overlayfs is present:
That storage is not specified in your global config:
And remove your local storage config:
Then just do:
And if it say following (like my podman 4.3.1 does):
It's defaulting to "vfs" storage, i.e. buggy. |
What are "most distros"? Ubuntu (22.04) does not install any "storage.conf":
nor have "storage" section in confs in /etc/containers/... |
I don't have an Ubuntu installation to try it out quickly, I'd need to setup a VM first. Can you please try the last version of Podman and confirm the issue still exists there? |
@giuseppe I tried on main if you remove all storage.conf files it will pick vfs on main. |
IMHO bug causing disks to run out of space is pretty critical, especially now that Podman is getting wider usage (e.g. Ubuntu added it only in latest LTS). This bug can make a single build to easily fill previously near-empty TB-sized disk. While the fix is fairly trivial (reset podman & add two line config), finding it can take time. |
@Luap99 thanks for checking that! @umohnani8 would you like to take a look at this one? |
@giuseppe I am happy to take a look at it, but I have limited availability the next two weeks. If this is time critical, I think it would be better for you to look into it instead. |
if there are no configuration files present, attempt to use overlay for rootless if fuse-overlayfs is installed or if the kernel is >= 5.13. Closes: containers#1570 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
sure, opened a PR here: #1571 |
if there are no configuration files present, attempt to use overlay for rootless if fuse-overlayfs is installed or if the kernel is >= 5.13. Closes: containers#1570 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
if there are no configuration files present, attempt to use overlay for rootless if fuse-overlayfs is installed or if the kernel is >= 5.13. Closes: containers#1570 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
if there are no configuration files present, attempt to use overlay for rootless if fuse-overlayfs is installed or if the kernel is >= 5.13. Closes: containers#1570 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
if there are no configuration files present, attempt to use overlay for rootless if fuse-overlayfs is installed or if the kernel is >= 5.13. Closes: containers#1570 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
if there are no configuration files present, attempt to use overlay for rootless if fuse-overlayfs is installed or if the kernel is >= 5.13. Closes: containers#1570 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
Issue Description
With default options, rootless podman build takes all disk space, using about 100x compared to docker.
Upstream release notes for newer Podman versions did not have any mention of fixing such issue, so I'm assuming that this bug is still valid.
Steps to reproduce the issue
Steps to reproduce the issue
sudo rm -rf ~/.config/containers/ ~/.local/share/containers/
podman build --format=docker --rm -t <tag> -f Dockerfile .
Describe the results you received
Podman uses hundreds of GBs to build few GB container, even after the container build has finished, due to defaulting to "vfs" driver, although "fuse-overlayfs" (1.7.1) is installed.
Describe the results you expected
Podman has sane disk usage, by defaulting to "overlay" storage driver when "fuse-overlayfs" is present: containers/podman#1726
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
No
Additional environment details
This is Ubuntu 23.04 "podman" package installed to Ubuntu 22.04 installation.
Additional information
This should have been fixed already before Podman v1.0 release: containers/podman#1726, so I guess it's a regression?
WA for the issue was found from here: containers/buildah#1040
The text was updated successfully, but these errors were encountered: