No, it does not: $ docker run -it system:0qjxd5ljsh316ki7wqkk2xz9b68lynh2 bash docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"bash\": executable file not found in $PATH": unknown.
It seems like some things which get set up when creating a regular system via `guix system` do not when specifying output as a Docker image. Unfortunately, the documentation doesn't explain much about how the system profile works, and I'm not knowledgeable enough about Guix to make an informed guess. On Wed, Nov 27, 2019 at 9:39 AM zimoun <[email protected]> wrote: > Hi, > > On Sun, 17 Nov 2019 at 18:17, Stephen Scheck <[email protected]> > wrote: > > > $ docker run -it system:0qjxd5ljsh316ki7wqkk2xz9b68lynh2 > > /run/current-system/profile/bin/bash --login > > docker: Error response from daemon: OCI runtime create failed: > > container_linux.go:348: starting container process caused "exec: > > \"/run/current-system/profile/bin/bash\": stat > > /run/current-system/profile/bin/bash: no such file or directory": > unknown. > > Does the command > > docker run -it system:0qjxd5ljsh316ki7wqkk2xz9b68lynh2 bash > > work? > > > All the best, > simon >
