Memory error about singularityhub.github.io

[vsoch]

ok, I'm testing this now. Thankfully I kept a boolean variable that can turn on/off using memory for the tar - you can imagine memory is a nice solution given that you have (smaller) images and want to do quick operations with the tar, but it's not optimal for this case! I will let you know when I finish testing and update singularity-python. I think it should be able to install the updated version (from pip) and we won't need to regenerate the builders, so we will have to test to see if it works. I'll let you know when to push again - stay tuned!

[vsoch]

ok (I think) this is where it bugged out before - generating the image:

>>> image_package = package(image_path=image,
...                                 spec_path=params['spec_file'],
...                                 output_folder=build_dir,
...                                 sudopw='',
...                                 remove_image=True,
...                                 verbose=True,
...                                 old_version=True)
DEBUG:shub_builder:Found runscript.
INFO:shub_builder:Adding software list to package.
DEBUG:shub_builder:Adding Singularity to package...
DEBUG:shub_builder:Adding VERSION to package...
DEBUG:shub_builder:Adding runscript to package...
DEBUG:shub_builder:Adding folders.txt to package...
DEBUG:shub_builder:Adding files.txt to package...
DEBUG:shub_builder:Package created at /tmp/build/image2.img.zip

the above is generated using the (old way) which is singularity export to a file (.tar) instead of to memory, and reading as bytes.

[vsoch]

oh by the way, there was one pip install that failed when I was testing, this one:

python3 -m pip install myavi
Collecting myavi
  Could not find a version that satisfies the requirement myavi (from versions: )
No matching distribution found for myavi

[vsoch]

okey doke - the new version (with old_version=True) to not use the memory tar is uploaded to pypi! If you wouldn't mind, could you commit again to trigger a build? If it's the case that the builder updates with pip, then it should build (or at least not hit that same bug). If it's the case that I need to update the builder itself, then you'll have to give me a bit more time to do that :) Thanks for your help with this!

[belledon]

Oops, sorry forgot to mention that I made another branch chainer_v2.0 without myavi. I triggered both now.

[belledon]

All good here. The container builds!

[vsoch]

Woohoo! So good to hear!! Feel free to close the issue, and please poke again if trouble arises.

[belledon]

Thanks again for all your help!