Both will be able to execute commands in container. Both could detach the container.
So what is the real difference between docker exec and docker attach?
There was a commit PR which added to the doc:
Note: This command (
attach
) is not for running a new process in a container. See:docker exec
.
The answer to "Docker. How to get bash\ssh inside runned container (run -d
)?" illustrates the difference:
(docker >= 1.3) If we use
docker attach
, we can use only one instance of shell.
So if we want to open new terminal with new instance of container's shell, we just need to rundocker exec
if the docker container was started using
/bin/bash
command, you can access it using attach, if not then you need to execute the command to create a bash instance inside the container usingexec
.
As mentioned in this issue:
- Attach isn't for running an extra thing in a container, it's for attaching to the running process.
- "
docker exec
" is specifically for running new things in a already started container, be it a shell or some other process.
The same issue adds:
While
attach
is not well named, particularly because of the LXC commandlxc-attach
(which is more akindocker exec <container> /bin/sh
, but LXC specific), it does have a specific purpose of literally attaching you to the process Docker started.
Depending on what the process is the behavior may be different, for instance attaching to/bin/bash
will give you a shell, but attaching to redis-server will be like you'd just started redis directly without daemonizing.