Germán Moltó

Hi @WinstonN. Thank you for your interest in SCAR. We are very happy to see that you are undertaking this proof of concept ahead. Unfortunately, we could not allocate time...

Ping @srisco

Hi, We deeply investigated this issue in the past and found absolutely no way to take advantage of this memory for POSIX-type file access. No Ramdisk can be created since...

Hi. Support for pulling images from AWS ECR should be implemented in udocker (not in SCAR). Last time we tested this (a year and a half ago) this support was...

For the sake of reference: https://github.com/indigo-dc/udocker/issues/168

Hi @adokter. Thank you for letting us know your use case. Perhaps you could use S3 as the storage back-end for the Docker images (see: https://scar.readthedocs.io/en/latest/advanced_usage.html#upload-docker-image-files-using-an-s3-bucket), instead of Docker Hub....

Hi @rmtuckerphx. Sorry for the delay. Thank you for your interest in SCAR. While we do not have an example that covers your use case, here are some hints: 1....

@eldos-dl No. The only working mode of udocker in AWS Lambda is the F1 execution mode.

For the sake of reference, this problem is also exhibited with the [openjdk:6-jre](https://hub.docker.com/r/library/openjdk/tags/6-jre/) image in Docker Hub. [openjdk:7-jre](https://hub.docker.com/r/library/openjdk/tags/7-jre/) does not fit within the 512 MB limits

The same obscure error is obtained when trying to create a function out of a file that references a non-existent file: ```sh unctions: scar-alpine: image: alpine memory: 128 init_script: non-existent-file.sh...