{"action":"closed","issue":{"url":"https://api.github.com/repos/singularityware/singularity/issues/572","repository_url":"https://api.github.com/repos/singularityware/singularity","labels_url":"https://api.github.com/repos/singularityware/singularity/issues/572/labels{/name}","comments_url":"https://api.github.com/repos/singularityware/singularity/issues/572/comments","events_url":"https://api.github.com/repos/singularityware/singularity/issues/572/events","html_url":"https://github.com/singularityware/singularity/issues/572","id":220297760,"number":572,"title":"think about non sudo ways to do a \"sort of\" bootstrap","user":{"login":"vsoch","id":814322,"avatar_url":"https://avatars3.githubusercontent.com/u/814322?v=3","gravatar_id":"","url":"https://api.github.com/users/vsoch","html_url":"https://github.com/vsoch","followers_url":"https://api.github.com/users/vsoch/followers","following_url":"https://api.github.com/users/vsoch/following{/other_user}","gists_url":"https://api.github.com/users/vsoch/gists{/gist_id}","starred_url":"https://api.github.com/users/vsoch/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vsoch/subscriptions","organizations_url":"https://api.github.com/users/vsoch/orgs","repos_url":"https://api.github.com/users/vsoch/repos","events_url":"https://api.github.com/users/vsoch/events{/privacy}","received_events_url":"https://api.github.com/users/vsoch/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":18,"created_at":"2017-04-07T18:49:38Z","updated_at":"2017-04-11T02:57:40Z","closed_at":"2017-04-11T02:57:40Z","body":"Given that a user wants to do operations on files, any of the following:\r\n\r\n- add or remove files from a tar that will be added to the container\r\n- add files from local host to container\r\n- add files from web address to container\r\n\r\nGiven that we stay true to maintaining permissions (eg if the user can't do it outside of container, shouldn't be able to do it inside) we could have something that looks like a \"non sudo\" bootstrap, but the %post would be removed. Instead, we would just have `%files` `%labels` and `%environment`, like\r\n\r\n```bash\r\nBootstrap: docker\r\nFrom: ubuntu:latest\r\n\r\n%files[add]\r\n/local/file /path/in/container\r\n\r\n%files[remove]\r\n/path/in/container\r\n```\r\n\r\nWe would just need a way to distinguish the context of the files command. In the example above, I'm using the similar approach that pip does when you install a particular version of a package, eg:\r\n\r\npip install package[tag]\r\n\r\nWe could also take a Dockerish approach, and just have ADD and REMOVE\r\n\r\n```bash\r\nBootstrap: docker\r\nFrom: ubuntu:latest\r\n\r\n%files\r\nADD /local/file /path/in/container\r\nREMOVE /path/in/container\r\n```\r\n \r\nwhich might make sense so the user can specify an ordering, and it fits with our current schema. We would want a user to be able to use the same bootstrap file for (with sudo) which would include `%post` and without sudo, which would not. Cool request by @satra ! Thoughts?\r\n"}}
{"actor":{"display_login":"vsoch"}}