-
-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--writable option for execute/run not working in spython #138
Comments
Hey this definitely looks like a bug - is it okay if I fix it tomorrow morning (it's getting late on the east coast). Also - you wanted another argument added to the command (could you share that here too?) I'll do both at the same time. |
Sure .Thanks a lot @vsoch. I wanted the |
Did you do something special with overlaw for the first? I'm getting the same thing for the singularity on the command line and spython execute: $ sudo singularity exec --writable busybox.sif touch /file
WARNING: While attempting to set up SIFOverlay: no SIF writable overlay partition found
touch: /file: Read-only file system |
Ah ok, building the sandbox works without that message, I'll use that to debug. |
Build: client.build('docker://debian:buster-slim', 'debian', sandbox=True, sudo=True) successful build of a sandbox: ls debian
bin/ dev/ etc/ lib/ media/ opt/ root/ sbin/ srv/ tmp/ var/
boot/ environment@ home/ lib64/ mnt/ proc/ run/ singularity@ sys/ usr/ Now issue touch command, two examples show getting just result, and getting return code too. $ client.execute('debian', 'touch /file', writable=True, sudo=True)
[]
$ client.execute('debian', 'touch /file', writable=True, sudo=True, return_result=True)
$ {'message': [], 'return_code': 0} and each of shell, exec, and run has added an options list (optional) where you can add client.execute('debian', 'touch /tmp/file', options=['--writable-tmpfs']) I'll open a PR for you to test shortly! |
Thanks ! I am checking it locally. |
Expected Behavior
I have a sandbox
debian/
built fromdebian.sif
.but on doing the same natively from terminal,
it works and the file gets created.
Actual Behavior
This step should work perfectly same like when done natively.
Steps to Reproduce
Then do the above mentioned steps.
Context
Failure Logs
The text was updated successfully, but these errors were encountered: