0ct0pu5/moby
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Fixed some typos and other issues from ostezer comments.

Browse source 
Docker-DCO-1.1-Signed-off-by: William Henry <whenry@redhat.com> (github: ipbabble)

 Changes to be committed:
	modified:   contrib/man/md/docker-build.1.md
	modified:   contrib/man/md/docker-run.1.md
	modified:   contrib/man/md/docker-tag.1.md
This commit is contained in:
William Henry 2014-05-31 15:44:17 -06:00
parent a14a88e53d
commit e471a87f19
3 changed files with 19 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
contrib/man/md/docker-build.1.md
View file

@ -70,29 +70,31 @@ specified within the `ADD` instruction into the specified target.
## Building an image and naming that image
A good practice is to give a name to the image you are building. There are
not hard rules here but it is best to give the names consideration.
no hard rules here but it is best to give the names consideration.
The **-t**/**--tag** flag is used to rename an image. Here are some examples:
Though t is not good practice, image names can be aribtrary:
Though it is not a good practice, image names can be arbtrary:
docker build -t myimage .
A better approach is provide a fully qualified and meaningful repository
name, name, and tag (where tag in this context means the qualifier after
the ":"). In this example we build a Jboss image for the Fedora repository
and give it a version 1.0:
A better approach is to provide a fully qualified and meaningful repository,
name, and tag (where the tag in this context means the qualifier after
the ":"). In this example we build a JBoss image for the Fedora repository
and give it the version 1.0:
docker build -t fedora/jboss:1.0
The next example is for the "whenry" user repository and uses Fedora and
JBoss and gives it a version 2.1 :
JBoss and gives it the version 2.1 :
docker build -t whenry/fedora-jboss:V2.1
Or:
If you do not provide a version tag then Docker will assign `latest`:
docker build -t whenry/fedora-jboss:latest
docker build -t whenry/fedora-jboss
When you list the images, the image above will have the tag `latest`.
So renaming an image is arbitrary but consideration should be given to
a useful convention that makes sense for consumers and should also take

4
contrib/man/md/docker-run.1.md
View file

@ -64,8 +64,8 @@ the other shell to view a list of the running containers. You can reattach to a
detached container with **docker attach**. If you choose to run a container in
the detached mode, then you cannot use the **-rm** option.
When attached in tty mode, you can detach from a running container by pressing
the keys ctrl+p ctrl+q.
When attached in the tty mode, you can detach from a running container without
stopping the process by pressing the keys CTRL-P CTRL-Q.
**--dns**=*IP-address*

11
contrib/man/md/docker-tag.1.md
View file

@ -9,7 +9,7 @@ docker-tag - Tag an image in the repository
IMAGE [REGISTRYHOST/][USERNAME/]NAME[:TAG]
# DESCRIPTION
This will rename an image in the repository. "Tag" is this context means the
This will rename an image in the repository. This refers to the
entire image name including the optional TAG after the ':'.
# "OPTIONS"
@ -27,15 +27,16 @@ separated by a ':'
The image name.
**TAG**
The tag you are assigning to the image. This is often a version or other
'tag' to distinguish from other similarly named images.
The tag you are assigning to the image. Though this is arbitrary it is
recommended to be used for a version to disinguish images with the same name.
Note that here TAG is a part of the overall name or "tag".
# EXAMPLES
## Tagging an image
Here is an example of renaming an image with the repository 'fedora', name
'httpd', and tag version1.0 :
Here is an example of renaming an image (e.g. 0e5574283393) as "httpd" and
tagging it into the "fedora" repository with "version1.0":
docker tag 0e5574283393 fedora/httpd:version1.0