Jason Stover

This ... wouldn't be that great. Are you basically doing something like: ``` mkdir -m 0777 /tmp/sing_cache ``` Then setting `SINGULARITY_CACHEDIR=/tmp/sing_cache` ? Every user, is going to have access to...

But the difference is that CACHE is a per user thing, not a system thing.

For the reason I gave. A shared cache means that every user has access to the cache files, even if they don't have access to the source. They can access...

You're missing the point ... Here, a quick hack. I made `/tmp/sing_cache/$USER` the cache directory. ``` # mkdir -m 1777 /tmp/sing_cache ``` So ... general default umask is `022` (or...

> using a shared cache at /root/.singularity It can't be a shared cache ... I'm betting it's because of things like: `sudo singularity build [...]` That's not a *shared* cache,...

@mr-c In the `docker://debian` image, at the end of the `/.singularity.d/runscript` file we have: ``` eval "set ${SINGULARITY_OCI_RUN}" exec "$@" ``` The `eval` call is to expand any variables prior...

I'm not sure there is anything you can do. When you do a `run`, there's an extra `eval` step that happens from the default runscript that gets generated. That parses...

There should be 2 places where `LOCKF` is removed in `wwgetfiles` .... 1) If `wget` fails when downloading a file, or 2) if `wget` fails when getting the list of...

Leave the copyright header and IMO you're fine. ;) Also don't change the `License:` entry, as that's the license of the Singularity software, not the file.

Right ... and as long as you leave the copyright header you're clear. You can relicense from OHPC under Apache 2 all you want. But to keep with the original...