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
I get no error message when committing a container fails due to a full hard drive.
This case is especially annoying because BB's output looks exactly like for a successful run.
I only detected this case because I had the --export flag enabled and it complained about not finding the required image.
Also the normal debug methods like containers/keep do not work (because there is no space to store the failed image`) so I had to manually trace back the steps to find the issue.
This is the output that buildah commit $image produces when run manually on the command line which clearly states the problem: error committing container "debian-working-container" to "": error copying layers and metadata for container "e6f6731588d816f51ffd6c752a903074b75a2c9c35e27305013f6a756825e1d7": Error initializing source containers-storage:debian-wor king-container: error storing layer "b85af40f2294f58d92e5b319b2bafd3c7198954ba8da06342e7fd2d2f0ffc3c4" to file: write /var/tmp/buildah307038400/layer: no space left on device ERRO exit status 125
The text was updated successfully, but these errors were encountered:
Same goes for some other commands btw., like export. It would probably be worth finding a common solution for all these non-layer-creating buildah commands.
I get no error message when committing a container fails due to a full hard drive.
This case is especially annoying because BB's output looks exactly like for a successful run.
I only detected this case because I had the
--export
flag enabled and it complained about not finding the required image.Also the normal debug methods like
containers/keep
do not work (because there is no space to store the failed image`) so I had to manually trace back the steps to find the issue.This is the output that
buildah commit $image
produces when run manually on the command line which clearly states the problem:error committing container "debian-working-container" to "": error copying layers and metadata for container "e6f6731588d816f51ffd6c752a903074b75a2c9c35e27305013f6a756825e1d7": Error initializing source containers-storage:debian-wor king-container: error storing layer "b85af40f2294f58d92e5b319b2bafd3c7198954ba8da06342e7fd2d2f0ffc3c4" to file: write /var/tmp/buildah307038400/layer: no space left on device ERRO exit status 125
The text was updated successfully, but these errors were encountered: