Closed superfell closed 1 year ago
I think probably the last command you ran in bob3 failed, like:
bob3% false
bob3% exit
Error: failed to run command in environment "bob3"
Caused by:
Non-zero exit status (1) from docker exec
Command exited with status 1 [this is output by Diego's shell prompt]
~$
Then the shell will exit with a non-zero status, and it looks to Cubicle like everything failed terribly. I don't know if there's a better way to handle this, other than having Cubicle ignore the exit status of interactive shells.
Docker seems to pass the exit status through but not display an error:
~$ docker run -it --rm debian
root@1686f5a4afd8:/# false
root@1686f5a4afd8:/#
exit
Command exited with status 1 [this is output by Diego's shell prompt]
~$ docker run -it --rm debian
root@9965e1ea7990:/# true
root@9965e1ea7990:/#
exit
~$
Ah, yes, that'd be it.
This is using #38 on arm/osx I
cub enter bob3
do some things, then useexit
to leave bob3. At which point i get an error