tldr/pages/common/docker.md

# docker

> Manage Docker containers and images.

- List currently running docker containers:

`docker container ls`

- List all docker containers (running and stopped):

`docker container ls -a`

- Start a container from an image, with a custom name:

`docker container run --name={{container_name}} {{image}}`

- Start or stop an existing container:

`docker container {{start|stop}} {{container_name}}`

- Start a container from an image and get a shell inside of it:

`docker container run -it {{image}} bash`

- Run a command inside of an already running container:

`docker container exec {{container_name}} {{command}}`

- Remove a stopped container:

`docker container rm {{container_name}}`

- Fetch and follow the logs of a container:

`docker container logs -f {{container_name}}`
Add Docker Added commonly used docker commands to list/start/stop containers. 2015-12-27 18:11:20 +00:00			`# docker`

Update docker description 2016-01-19 22:48:21 +00:00			`> Manage Docker containers and images.`
Add Docker Added commonly used docker commands to list/start/stop containers. 2015-12-27 18:11:20 +00:00
docker: minor tweak to first description change "List" from a noun to a verb, to match the project's guidelines. 2017-04-27 23:55:32 +01:00			`- List currently running docker containers:`
Add Docker Added commonly used docker commands to list/start/stop containers. 2015-12-27 18:11:20 +00:00
docker: update docker commands to conform to Docker 1.13 (#1505) 2017-09-28 10:25:00 +01:00			`docker container ls`
Add Docker Added commonly used docker commands to list/start/stop containers. 2015-12-27 18:11:20 +00:00
Formatted all pages according to guidelines. 2016-01-07 17:31:27 +00:00			`- List all docker containers (running and stopped):`
Add Docker Added commonly used docker commands to list/start/stop containers. 2015-12-27 18:11:20 +00:00
docker: update docker commands to conform to Docker 1.13 (#1505) 2017-09-28 10:25:00 +01:00			`docker container ls -a`
Add Docker Added commonly used docker commands to list/start/stop containers. 2015-12-27 18:11:20 +00:00
docker: combine start/stop, add basic run example (#2363) The start and stop examples are pretty much identical, so it doesn't make sense to use up the space of two examples in the limited length of a tldr page (especially for such a complex command as docker). In the slot left by combining the two entries, a new one is added mentioning how to launch a container from an image. Placing this example before the start/stop commands (and naming the parameter "container_name" consistently trhoughout the page) also makes the sequence more logical, by first explaining how containers are instantiated, and only then mentioning how they are managed. 2018-10-01 17:20:57 +01:00			`- Start a container from an image, with a custom name:`
Add Docker Added commonly used docker commands to list/start/stop containers. 2015-12-27 18:11:20 +00:00
docker: combine start/stop, add basic run example (#2363) The start and stop examples are pretty much identical, so it doesn't make sense to use up the space of two examples in the limited length of a tldr page (especially for such a complex command as docker). In the slot left by combining the two entries, a new one is added mentioning how to launch a container from an image. Placing this example before the start/stop commands (and naming the parameter "container_name" consistently trhoughout the page) also makes the sequence more logical, by first explaining how containers are instantiated, and only then mentioning how they are managed. 2018-10-01 17:20:57 +01:00			`docker container run --name={{container_name}} {{image}}`
Add Docker Added commonly used docker commands to list/start/stop containers. 2015-12-27 18:11:20 +00:00
docker: combine start/stop, add basic run example (#2363) The start and stop examples are pretty much identical, so it doesn't make sense to use up the space of two examples in the limited length of a tldr page (especially for such a complex command as docker). In the slot left by combining the two entries, a new one is added mentioning how to launch a container from an image. Placing this example before the start/stop commands (and naming the parameter "container_name" consistently trhoughout the page) also makes the sequence more logical, by first explaining how containers are instantiated, and only then mentioning how they are managed. 2018-10-01 17:20:57 +01:00			`- Start or stop an existing container:`
Add Docker Added commonly used docker commands to list/start/stop containers. 2015-12-27 18:11:20 +00:00
docker: combine start/stop, add basic run example (#2363) The start and stop examples are pretty much identical, so it doesn't make sense to use up the space of two examples in the limited length of a tldr page (especially for such a complex command as docker). In the slot left by combining the two entries, a new one is added mentioning how to launch a container from an image. Placing this example before the start/stop commands (and naming the parameter "container_name" consistently trhoughout the page) also makes the sequence more logical, by first explaining how containers are instantiated, and only then mentioning how they are managed. 2018-10-01 17:20:57 +01:00			`docker container {{start\|stop}} {{container_name}}`
adds commands for working with images 2015-12-29 04:25:31 +00:00
Formatted all pages according to guidelines. 2016-01-07 17:31:27 +00:00			`- Start a container from an image and get a shell inside of it:`
adds commands for working with images 2015-12-29 04:25:31 +00:00
docker: update docker commands to conform to Docker 1.13 (#1505) 2017-09-28 10:25:00 +01:00			`docker container run -it {{image}} bash`
adds commands for working with images 2015-12-29 04:25:31 +00:00
Formatted all pages according to guidelines. 2016-01-07 17:31:27 +00:00			`- Run a command inside of an already running container:`
adds commands for working with images 2015-12-29 04:25:31 +00:00
docker: combine start/stop, add basic run example (#2363) The start and stop examples are pretty much identical, so it doesn't make sense to use up the space of two examples in the limited length of a tldr page (especially for such a complex command as docker). In the slot left by combining the two entries, a new one is added mentioning how to launch a container from an image. Placing this example before the start/stop commands (and naming the parameter "container_name" consistently trhoughout the page) also makes the sequence more logical, by first explaining how containers are instantiated, and only then mentioning how they are managed. 2018-10-01 17:20:57 +01:00			`docker container exec {{container_name}} {{command}}`
docker: added rm command (#1297) 2017-03-16 04:37:17 +00:00
docker: update docker commands to conform to Docker 1.13 (#1505) 2017-09-28 10:25:00 +01:00			`- Remove a stopped container:`
docker: added rm command (#1297) 2017-03-16 04:37:17 +00:00
docker: combine start/stop, add basic run example (#2363) The start and stop examples are pretty much identical, so it doesn't make sense to use up the space of two examples in the limited length of a tldr page (especially for such a complex command as docker). In the slot left by combining the two entries, a new one is added mentioning how to launch a container from an image. Placing this example before the start/stop commands (and naming the parameter "container_name" consistently trhoughout the page) also makes the sequence more logical, by first explaining how containers are instantiated, and only then mentioning how they are managed. 2018-10-01 17:20:57 +01:00			`docker container rm {{container_name}}`
docker: add docker container logs example (#1680) 2017-11-27 18:14:42 +00:00
			`- Fetch and follow the logs of a container:`

docker: combine start/stop, add basic run example (#2363) The start and stop examples are pretty much identical, so it doesn't make sense to use up the space of two examples in the limited length of a tldr page (especially for such a complex command as docker). In the slot left by combining the two entries, a new one is added mentioning how to launch a container from an image. Placing this example before the start/stop commands (and naming the parameter "container_name" consistently trhoughout the page) also makes the sequence more logical, by first explaining how containers are instantiated, and only then mentioning how they are managed. 2018-10-01 17:20:57 +01:00			`docker container logs -f {{container_name}}`