67735d2a16
See #10141 for more info, but the main point of this is to make sure that if you do "docker run -e FOO ..." that FOO from the current env is passed into the container. This means that if there's a value, its set. But it also means that if FOO isn't set then it should be unset in the container too - even if it has to remove it from the env. So, unset HOSTNAME docker run -e HOSTNAME busybox env should _NOT_ show HOSTNAME in the list at all Closes #10141 Signed-off-by: Doug Davis <dug@us.ibm.com> |
||
---|---|---|
.github | ||
cli | ||
cmd/docker | ||
dockerfiles | ||
opts | ||
script/validate | ||
scripts/build | ||
vendor | ||
.dockerignore | ||
.gitignore | ||
LICENSE | ||
MAINTAINERS | ||
Makefile | ||
NOTICE | ||
README.md | ||
circle.yml | ||
docker.Makefile | ||
gometalinter.json | ||
poule.yml | ||
vendor.conf |
README.md
docker/cli
This repository is the home of the cli used in the Docker CE and Docker EE products.
It's composed of 3 main folders
/cli
- all the commands code./cmd/docker
- the entrypoint of the cli, aka the main.
Development
Build locally
$ make build
$ make clean
You will need gox for this one:
$ make cross
If you don't have gox, you can use the "in-container" version of make cross
, listed below.
Build inside container
$ make -f docker.Makefile build
$ make -f docker.Makefile clean
$ make -f docker.Makefile cross
In-container development environment
$ make -f docker.Makefile dev
Then you can use the build locally commands:
$ make build
$ make clean
Legal
Brought to you courtesy of our legal counsel. For more context, please see the NOTICE document in this repo.
Use and transfer of Docker may be subject to certain restrictions by the United States and other governments.
It is your responsibility to ensure that your use and/or transfer does not violate applicable laws.
For more information, please see https://www.bis.doc.gov
Licensing
docker/cli is licensed under the Apache License, Version 2.0. See LICENSE for the full license text.