Douglas Jacobsen

I wrote on 2015/12/22: The user-requested bind mounts (i.e., using --volume) can only perform bind mounts within the container, I think (I'll re-read this shortly, as I'm mucking with related...

Hi Miguel, /proc/mounts is probably not the proper file to read in a chroot (and/or container) environment. Try reading /proc/self/mounts instead. -Doug

Hi Alan, Could you please confirm which commit-level you're seeing this on? I suspect this may be fixed in 504742514460f97755d0b805be86a6e2302019dc from August 17. Thanks, Doug

Please consider looking at c7b22c4fcf8fa63b4741b346e0bfb61d2e38b4e5 (yesterday); it doesn't have relevance on specifically on this matter but corrects a number of other items.

shifter explicitly ignores sigterm/sigint/sighup/sigstop during container setup, however, it restores the original handlers (whatever they might have been) immediately before execution of the targeted process. during interactive setup (i.e., without...

Hello, Sorry about this! Was a problem with the documentation, the field was updated to use the same code as the VolumeMap stuff (originally developed for the user-requested volume mounts)....

Hi Miguel, We're starting work on a new feature using overlayfs that may allow some of what you're looking for. The ext4 stuff would still need to be mounted readonly...

sure, there have been two issues with using a passwd and group file in etcFiles 1) in the NERSC deployment we've had a cron job generate the files, which meant...

I can make this optional, i.e., not fail if resolv.conf does not exist. I'm wondering if there is a problem with the container being able to define its own resolv.conf....

Commit d483c7a, b711d6d, and 2b7350c address the password file aspects of this; Still need to resurrect the indirect prolog that uses the Cray NHC daemons to launch setupRoot/unsetupRoot.