Open tbooth opened 9 years ago
Shouldn't this work around it? I'm confused?
tbooth@balisaur[tbooth] env SHELL=/bin/bash oswitch avilella/qiime
exec: "zsh": executable file not found in $PATHFATA[0000] Error response from daemon: Cannot start container 852b2eddfde0af772d46b76e213e24fac47f90386f6ce5ebc2e55e6ac26794e6: exec: "zsh": executable file not found in $PATH
Only if you delete the bells-and-whistles image oswitch created and run again. Should this be the default behaviour? Probably yes. The current behaviour is a leftover from when I switched to dynamically switchifying images instead of having all images inherit from an oswitch base image. Back then oswitch used su -l
to change user in the container instead of using docker's USER directive. And so it was helpful to set login shell for the user created inside the container (people don't switch shells often). But with the new approach, the shell to execute is passed to the docker image by oswitch. So SHELL=/bin/bash
should override.
Consider using docker to get into the image to debug things while I fix this issue? The image oswitch created will be listed in docker images
as "oswitch_*_qiime".
Still looking into this, and whether it is really a problem with my chosen container, but here is the initial error:
That's OK, so: