Guest24897
/
DockerCLI
mirror of https://github.com/docker/cli.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

pass --change changes to the import job 

Docker-DCO-1.1-Signed-off-by: Dan Walsh <dwalsh@redhat.com> (github: rhatdan)
This commit is contained in:
Dan Walsh 2015-02-05 12:26:05 +01:00 committed by Tibor Vass
parent 6042a6f9a4
commit 99ef14ddab
1 changed files with 19 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
docs/sources/reference/commandline/cli.md
View File

@ -694,7 +694,7 @@ you refer to it on the command line.
Create a new image from a container's changes Create a new image from a container's changes
-a, --author="" Author (e.g., "John Hannibal Smith <hannibal@a-team.com>") -a, --author="" Author (e.g., "John Hannibal Smith <hannibal@a-team.com>")
-c, --change=[] Apply a modification in Dockerfile format before committing the image -c, --change=[] Apply specified Dockerfile instructions while committing the image
-m, --message="" Commit message -m, --message="" Commit message
-p, --pause=true Pause container during commit -p, --pause=true Pause container during commit
@ -709,7 +709,12 @@ while the image is committed. This reduces the likelihood of
encountering data corruption during the process of creating the commit. encountering data corruption during the process of creating the commit.
If this behavior is undesired, set the 'p' option to false. If this behavior is undesired, set the 'p' option to false.
#### Commit an existing container The `--change` option will apply `Dockerfile` instructions to the image
that is created.
Supported `Dockerfile` instructions: `CMD`, `ENTRYPOINT`, `ENV`, `EXPOSE`,
`ONBUILD`, `USER`, `VOLUME`, `WORKDIR`
#### Commit a container
$ sudo docker ps $ sudo docker ps
ID IMAGE COMMAND CREATED STATUS PORTS ID IMAGE COMMAND CREATED STATUS PORTS
@ -721,7 +726,7 @@ If this behavior is undesired, set the 'p' option to false.
REPOSITORY TAG ID CREATED VIRTUAL SIZE REPOSITORY TAG ID CREATED VIRTUAL SIZE
SvenDowideit/testimage version3 f5283438590d 16 seconds ago 335.7 MB SvenDowideit/testimage version3 f5283438590d 16 seconds ago 335.7 MB
#### Commit an existing container with new configurations #### Commit a container with new configurations
$ sudo docker ps $ sudo docker ps
ID IMAGE COMMAND CREATED STATUS PORTS ID IMAGE COMMAND CREATED STATUS PORTS
@ -1151,11 +1156,18 @@ NOTE: Docker will warn you if any containers exist that are using these untagged
tarball (.tar, .tar.gz, .tgz, .bzip, .tar.xz, .txz) into it, then tarball (.tar, .tar.gz, .tgz, .bzip, .tar.xz, .txz) into it, then
optionally tag it. optionally tag it.
-c, --change=[] Apply specified Dockerfile instructions while importing the image
URLs must start with `http` and point to a single file archive (.tar, URLs must start with `http` and point to a single file archive (.tar,
.tar.gz, .tgz, .bzip, .tar.xz, or .txz) containing a root filesystem. If .tar.gz, .tgz, .bzip, .tar.xz, or .txz) containing a root filesystem. If
you would like to import from a local directory or archive, you can use you would like to import from a local directory or archive, you can use
the `-` parameter to take the data from `STDIN`. the `-` parameter to take the data from `STDIN`.
The `--change` option will apply `Dockerfile` instructions to the image
that is created.
Supported `Dockerfile` instructions: `CMD`, `ENTRYPOINT`, `ENV`, `EXPOSE`,
`ONBUILD`, `USER`, `VOLUME`, `WORKDIR`
#### Examples #### Examples
**Import from a remote location:** **Import from a remote location:**
@ -1174,6 +1186,10 @@ Import to docker via pipe and `STDIN`.
$ sudo tar -c . | sudo docker import - exampleimagedir $ sudo tar -c . | sudo docker import - exampleimagedir
**Import from a local directory with new configurations:**
$ sudo tar -c . | sudo docker import --change "ENV DEBUG true" - exampleimagedir
Note the `sudo` in this example – you must preserve Note the `sudo` in this example – you must preserve
the ownership of the files (especially root ownership) during the the ownership of the files (especially root ownership) during the
archiving with tar. If you are not root (or the sudo command) when you archiving with tar. If you are not root (or the sudo command) when you