kotovalexarian-likes-github/moby--moby
1
0
Fork 0
mirror of https://github.com/moby/moby.git synced 2022-11-09 12:21:53 -05:00
Code Releases Activity

rebased, the clean up of the first few paragraphs of getting started with containers; addressed nit

Browse source 
Signed-off-by: Mike Brown <brownwm@us.ibm.com>
This commit is contained in:
Mike Brown 2015-09-14 09:26:32 -05:00
parent 621143a641
commit ff61be9b04
1 changed files with 18 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

28
docs/articles/basics.md
View file

@ -10,8 +10,8 @@ parent = "smn_containers"
# Get started with containers # Get started with containers
This guide assumes you have a working installation of Docker. To verify Docker is This guide assumes you have a working installation of Docker. To verify Docker
installed, use the following command: is installed, use the following command:
# Check that you have a working install # Check that you have a working install
$ docker info $ docker info
@ -19,12 +19,14 @@ installed, use the following command:
If you get `docker: command not found` or something like If you get `docker: command not found` or something like
`/var/lib/docker/repositories: permission denied` you may have an `/var/lib/docker/repositories: permission denied` you may have an
incomplete Docker installation or insufficient privileges to access incomplete Docker installation or insufficient privileges to access
Docker on your machine. Docker on your machine. With the default installation of Docker `docker`
commands need to be run by a user that is in the `docker` group or by the
`root` user.
Additionally, depending on your Docker system configuration, you may be required Depending on your Docker system configuration, you may be required
to preface each `docker` command with `sudo`. To avoid having to use `sudo` with to preface each `docker` command with `sudo`. One way to avoid having to use
the `docker` command, your system administrator can create a Unix group called `sudo` with the `docker` commands is to create a Unix group called `docker` and
`docker` and add users to it. add users that will be entering `docker` commands to the 'docker' group.
For more information about installing Docker or `sudo` configuration, refer to For more information about installing Docker or `sudo` configuration, refer to
the [installation](/installation) instructions for your operating system. the [installation](/installation) instructions for your operating system.
@ -53,9 +55,13 @@ To run an interactive shell in the Ubuntu image:
$ docker run -i -t ubuntu /bin/bash $ docker run -i -t ubuntu /bin/bash
The `-i` flag starts an interactive container. The `-t` flag creates a pseudo-TTY that attaches `stdin` and `stdout`. The `-i` flag starts an interactive container. The `-t` flag creates a
pseudo-TTY that attaches `stdin` and `stdout`.
To detach the `tty` without exiting the shell, use the escape sequence `Ctrl-p` + `Ctrl-q`. The container will continue to exist in a stopped state once exited. To list all containers, stopped and running use the `docker ps -a` command. To detach the `tty` without exiting the shell, use the escape sequence
`Ctrl-p` + `Ctrl-q`. The container will continue to exist in a stopped state
once exited. To list all containers, stopped and running, use the `docker ps -a`
command.
## Bind Docker to another host/port or a Unix socket ## Bind Docker to another host/port or a Unix socket
@ -171,7 +177,9 @@ TCP and a Unix socket
Save your containers state to an image, so the state can be Save your containers state to an image, so the state can be
re-used. re-used.
When you commit your container, Docker only stores the diff (difference) between the source image and the current state of the container's image. To list images you already have, use the `docker images` command. When you commit your container, Docker only stores the diff (difference) between
the source image and the current state of the container's image. To list images
you already have, use the `docker images` command.
# Commit your container to a new named image # Commit your container to a new named image
$ docker commit <container> <some_name> $ docker commit <container> <some_name>