DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Keep Your Application Secrets Secret
  • 3 Easy Steps for a (Dev)Containerized Microservice With Jolie and Docker
  • Containerize Gradle Apps and Deploy to Kubernetes With JKube Kubernetes Gradle Plugin
  • Deploy an ASP.NET Core Application in the IBM Cloud Code Engine

Trending

  • How to Submit a Post to DZone
  • Designing Memory Architecture for Stateful AI Agents: Short-Term Context and Long-Term Persistence
  • Part 4: Multi-Agent Orchestration — Pairing Goose With Quarkus Flow State Machines
  • MQTT, Kafka, NATS, or Zenoh? Choosing Edge-to-Cloud Messaging by Traffic Pattern

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

  1. DZone
  2. Software Design and Architecture
  3. Cloud Architecture
  4. Attach a Shell to Docker Container [quick tip]

Attach a Shell to Docker Container [quick tip]

Often there is a need to attach a shell to an already running Docker container. This is very useful, especially for debugging. This blog will explain how to attach a shell to an already running Docker container.

By 
Arun Gupta
·
Nov. 28, 15 · Tutorial
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
9.3K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

Docker Logo

Often there is a need to attach a shell to an already running Docker container. This is very useful, especially for debugging. This blog will explain how to attach a shell to an already running Docker container.

So, let’s say you run a Couchbase Docker container in detached mode:


1 2 3 4   > docker run -d couchbase/server 02061ddf0a3d1b2806a1ee6e354f4064d9d2ff4d84d8c96c0273c8883917a92f  

Running the container gives you the complete container id, 02061ddf0a3d1b2806a1ee6e354f4064d9d2ff4d84d8c96c0273c8883917a92f in this case.

This can be verified as:


1 2 3 4 5   > docker ps CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                                                        NAMES 02061ddf0a3d        couchbase/server    "/entrypoint.sh couch"   38 seconds ago      Up 37 seconds       8091-8093/tcp, 11207/tcp, 11210-11211/tcp, 18091-18092/tcp   clever_hypatia  

Or complete container id can be verified as:


1 2 3 4 5   > docker ps --no-trunc CONTAINER ID                                                       IMAGE               COMMAND                             CREATED              STATUS              PORTS                                                        NAMES 02061ddf0a3d1b2806a1ee6e354f4064d9d2ff4d84d8c96c0273c8883917a92f   couchbase/server    "/entrypoint.sh couchbase-server"   About a minute ago   Up 59 seconds       8091-8093/tcp, 11207/tcp, 11210-11211/tcp, 18091-18092/tcp   clever_hypatia  

Attach Shell to Docker Container

Bash shell can be attached to an already running container using docker exec -it {CID} bash. The {CID} can be the complete container id, truncated container id, or even the first few digits of the container ids amongst all the currently running containers.

So, the following three commands are equivalent in our case:

Attach Using Complete Container Id


1 2 3 4   > docker exec -it 02061ddf0a3d1b2806a1ee6e354f4064d9d2ff4d84d8c96c0273c8883917a92f bash root@02061ddf0a3d:/#  

Attach Using Truncated Container Id


1 2 3 4   > docker exec -it 02061ddf0a3d bash root@02061ddf0a3d:/#  

Attach Using Unique Numbers From Container Id


1 2 3 4   > docker exec -it 0 bash root@02061ddf0a3d:/#  

In this case, just specifying 0 would work because this is the only running container. If multiple containers are running that have 0 as the starting number, then the first few digits that make the container id unique are required.

Enjoy!

Docker (software) shell

Published at DZone with permission of Arun Gupta. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Keep Your Application Secrets Secret
  • 3 Easy Steps for a (Dev)Containerized Microservice With Jolie and Docker
  • Containerize Gradle Apps and Deploy to Kubernetes With JKube Kubernetes Gradle Plugin
  • Deploy an ASP.NET Core Application in the IBM Cloud Code Engine

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook