You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I need help finding the source of an issue with distrobox, because I don't have the technical capacity to pin-point its origin.
Basically, I am using scons to build a very big project (gem5), and if using distrobox (or even toolbx), i get an error 134. That means memory ran out. However, when building with scons in a classic podman container, it works! No memory limitations suddenly!
Desktop (please complete the following information):
Are you using podman, docker or lilipod?
podman
Which version or podman, docker or lilipod?
podman version 5.3.2
Which version of distrobox?
distrobox: 1.8.1.2
Which host distribution?
Fedora 41
How did you install distrobox?
rpm-ostree/dnf, fedora's official repo
Additional context
When I check memory usage while building, the process aborts before even using any significant memory usage. I know this doesn't come from gem5, as the building issue only happens when in a distrobox/toolbx container.
The text was updated successfully, but these errors were encountered:
Describe the bug
I need help finding the source of an issue with distrobox, because I don't have the technical capacity to pin-point its origin.
Basically, I am using scons to build a very big project (gem5), and if using distrobox (or even toolbx), i get an error 134. That means memory ran out. However, when building with scons in a classic podman container, it works! No memory limitations suddenly!
To Reproduce
Try to build the gem5 project (https://github.com/gem5/gem5).
Expected behavior
Memory should not run out, as host ressources are more than sufficient.
Logs
This is really hard to trace. SCons doesn't give anything apart
error 134
.Here is the core dump from the container:
Desktop (please complete the following information):
Additional context
When I check memory usage while building, the process aborts before even using any significant memory usage. I know this doesn't come from gem5, as the building issue only happens when in a distrobox/toolbx container.
The text was updated successfully, but these errors were encountered: