-
-
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
instance.run_command not working + Client.execute problem #213
Comments
Let's start with the first issue posted above, which is fixed here #214 (pending your testing and approval) then (from that branch) let's update the thread here (or open a new issue) with a specific way to reproduce your second. Thanks! |
#214 tested and it ran smoothly. thanks for the fix. eric |
Merged! If you want to install the master branch, and test again and update the issue for the second item, I'll have some time tomorrow or this weekend to work on it (going to bed now). Thanks! |
great. I'm currently playing some tests in order to check the second problem. PS have a good night ;-) Eric |
I guess I miss-use or at least does not understand the diffrences beetween see:
NB of course:
does it looks accurate for you ? |
and finally problem 2 is not a problem... adding eric |
No worries! So |
yep agree. seems more logical |
Hello,
while testing
singularity-cli
I encountered a problem withinstance.run_command
method.see:
I tested
instance.run_command
method as I have a problem withClient.execute
methodI have a singularity image that I need to test if it have nv support at runtime. from a different process than the one that instanciated it.
remember instance
a
was instanciated WITHOUT nv support in process1 but...in process2
NB as expected instance.option is not available from different process
singularity --version
apptainer version 1.2.4-1.el8
python3 --version
Python 3.8.1
The text was updated successfully, but these errors were encountered: