Is there any way to get a shell from running container?

[rezakamalifard]

Hi there,
Sometimes we need to get bash or ssh into a running container for debugging . Is it possible to do this with these images ?

[mattmoor]

The :debug tagged images container busybox, so you can --entrypoint=sh, but the :latest images drop this to bias towards minimal containers in production.

[rezakamalifard]

Thanks for your reply. So there is no busybox or any kind of shell in production images?

…

On Wed, Mar 7, 2018 at 02:19 Matt Moore ***@***.***> wrote: The :debug tagged images container busybox, so you can --entrypoint=sh, but the :latest images drop this to bias towards minimal containers in production. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#168 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABbb2pPkevKMO_50Oy47MyYNfpARbzPMks5tbxJggaJpZM4Sfi0J> .

[mattmoor]

Not currently, no. On Tue, Mar 6, 2018, 2:56 PM Reza Kamalifard <notifications@github.com> wrote:

…

Thanks for your reply. So there is no busybox or any kind of shell in production images? On Wed, Mar 7, 2018 at 02:19 Matt Moore ***@***.***> wrote: > The :debug tagged images container busybox, so you can --entrypoint=sh, > but the :latest images drop this to bias towards minimal containers in > production. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > < #168 (comment) >, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/ABbb2pPkevKMO_50Oy47MyYNfpARbzPMks5tbxJggaJpZM4Sfi0J > > . > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#168 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACVE4kt4abAm1ViQ2L1LguAwiuC9DaxRks5tbxQLgaJpZM4Sfi0J> .

[dubek]

@itmard You can copy the busybox into a running container and then run it there. If you have a running container named mycontainer1, you can run:

docker cp /path/to/busybox mycontainer1:/sh
docker cp /path/to/busybox mycontainer1:/ls
docker exec -it mycontainer1 /sh
# /ls
...

The busybox executable can be extracted from the busybox:latest docker image, for example. Make sure it is statically linked:

$ file busybox
busybox: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, stripped

[dlorenc]

Closing as this looks addressed. Also see kubernetes/enhancements#277 for another take on a similar use-case.