out of space errors are ignored, container shows as complete on hub UI about singularityhub.github.io

[fac2003]

You can find an example of this here:
https://singularity-hub.org/containers/1406/log

INFO:shub_builder:Checking out branch master
Already on 'master'
Your branch is up-to-date with 'origin/master'.
INFO:shub_builder:Checking out commit 8336d1ffac6e1dc6a9f76c0cac51815547d1310b
INFO:shub_builder:Found spec file Singularity in repository
DEBUG:shub_builder:Building in directory /tmp/tmpd_4yb0l7
DEBUG:shub_builder:Spec file set to Singularity
DEBUG:shub_builder:Spec file for build should be in /tmp/tmpd_4yb0l7/Singularity
tar: var/cache/yum/x86_64/7/updates/gen/primary_db.sqlite: Wrote only 5120 of 10240 bytes
tar: var/lib/rpm/Basenames: Wrote only 8192 of 10240 bytes
tar: var/lib/rpm/Dirnames: Wrote only 9216 of 10240 bytes
tar: var/lib/rpm/Packages: Wrote only 9728 of 10240 bytes
tar: var/lib/rpm/Requirename: Wrote only 2560 of 10240 bytes
tar: var/lib/rpm/Sha1header: Wrote only 1024 of 5120 bytes
tar: var/lib/yum/history/2017-06-05/13: Cannot mkdir: No space left on device
tar: var/lib/yum/history/2017-06-05/13: Cannot mkdir: No space left on device
tar: var/lib/yum/history/2017-06-05/13/config-main: Cannot open: No such file or directory
tar: var/lib/yum/history/2017-06-05/13: Cannot mkdir: No space left on device
tar: var/lib/yum/history/2017-06-05/13/config-repos: Cannot open: No such file or directory
tar: var/lib/yum/history/2017-06-05/13: Cannot mkdir: No space left on device
tar: var/lib/yum/history/2017-06-05/13/saved_tx: Cannot open: No such file or directory
tar: var/lib/yum/history/history-2017-06-05.sqlite: Wrote only 1024 of 10240 bytes
tar: var/lib/yum/rpmdb-indexes/pkgtups-checksums: Wrote only 6656 of 10240 bytes

and so on, but the container looks complete:

[vsoch]

Hey @fac2003 ! This is unlikely to be the instance, but the container itself. Try setting the size to a larger one in build settings and see if it completes. The reason it is deemed to be ok is because the extracted files don't seem to influence some kind of image being successfully built, which runs with a simple ls command.

[fac2003]

Thanks for the tip. It's a problem that you can't trust the image was successfully built by just looking at the UI. S
In this case the %post statements never ran, that seems a bit strange to consider it successful.

[vsoch]

I can't implement a test that is general enough to fit all containers - but there is a solution! This is exactly why we have the %test section - you can write tests and it will fail if they don't pass. Do you want to give it a try?

[fac2003]

Thanks, I am trying this now. The documentation of the %test section is lacking in specifics. I assume returning a non zero status is an error code, but I would have liked this written in the doc (http://singularity.lbl.gov/docs-bootstrap).

[vsoch]

Definitely! Here is the (probably lacking) test section - http://singularity.lbl.gov/docs-bootstrap#test if you have specifics you are wanting to add, I'd be happy to tweak! I think that's about the extent of what test is, so it's all that I wrote :P

[vsoch]

I added some docs here https://github.com/singularityhub/singularityhub.github.io/wiki/Generate-Images#add-tests to make it easier to find this information as well, at least the bits relevant to Singularity Hub!