Closed bneron closed 3 years ago
It’s likely it ran out of disk space or memory, can you give me estimates times and sizes? Also remember it’s a small instance - the build probably takes longer in shub.
below the output of /usr/bin/time --verbose sudo singularity build bioconvert Singularity
Command being timed: "sudo singularity build bioconvert Singularity"
User time (seconds): 910.82
System time (seconds): 70.77
Percent of CPU this job got: 149%
Elapsed (wall clock) time (h:mm:ss or m:ss): 10:57.38
Average shared text size (kbytes): 0
Average unshared data size (kbytes): 0
Average stack size (kbytes): 0
Average total size (kbytes): 0
Maximum resident set size (kbytes): 2248952
Average resident set size (kbytes): 0
Major (requiring I/O) page faults: 0
Minor (reclaiming a frame) page faults: 15933704
Voluntary context switches: 341316
Involuntary context switches: 161448
Swaps: 0
File system inputs: 408
File system outputs: 14056608
Socket messages sent: 0
Socket messages received: 0
Signals delivered: 0
Page size (bytes): 4096
Exit status: 0
the size of the final image is 846M
I don't know @bneron , if the image doesn't build, it typically means what I stated above, or that something that the build needs isn't available in secure build. The only other thing that would be an issue is if you cleared out /tmp, which I don't see you doing. It's very likely that the instance is just small, and it ran out of memory for the actual generation of the container, and the exit code was 1. You could try a different builder, or do toy tests with the current builder and see if something smaller / shorter works okay.
Link to Container Collection Log, Build, or Collection (in that order)
https://singularity-hub.org/containers/10747/log https://singularity-hub.org/collections/135
Behavior when Building Locally
The container build normally
see build_log.tx attached to have the complete local build log build_log.txt
singularity version 3.3.0-1
Error on Singularity Hub
but after this output we have trace thath should happen during the %post step
What do you think is going on?
It's like singularity try to build image whereas the post phase is not finish