请告诉我命令之间的差异docker container run
VS docker run
还什么VS docker build
泊坞窗命令相当于
Q
泊坞窗命令相当于
0
A
回答
0
docker image build
之间的差别,如果你只是运行泊坞窗命令
$ docker
Usage: docker COMMAND
A self-sufficient runtime for containers
Options:
--config string Location of client config files (default "/Users/tarun.lalwani/.docker")
-D, --debug Enable debug mode
--help Print usage
-H, --host list Daemon socket(s) to connect to
-l, --log-level string Set the logging level ("debug"|"info"|"warn"|"error"|"fatal") (default "info")
--tls Use TLS; implied by --tlsverify
--tlscacert string Trust certs signed only by this CA (default "/Users/tarun.lalwani/.docker/ca.pem")
--tlscert string Path to TLS certificate file (default "/Users/tarun.lalwani/.docker/cert.pem")
--tlskey string Path to TLS key file (default "/Users/tarun.lalwani/.docker/key.pem")
--tlsverify Use TLS and verify the remote
-v, --version Print version information and quit
Management Commands:
checkpoint Manage checkpoints
config Manage Docker configs
container Manage containers
image Manage images
network Manage networks
node Manage Swarm nodes
plugin Manage plugins
secret Manage Docker secrets
service Manage services
stack Manage Docker stacks
swarm Manage Swarm
system Manage Docker
volume Manage volumes
Commands:
attach Attach local standard input, output, and error streams to a running container
build Build an image from a Dockerfile
commit Create a new image from a container's changes
cp Copy files/folders between a container and the local filesystem
create Create a new container
deploy Deploy a new stack or update an existing stack
diff Inspect changes to files or directories on a container's filesystem
events Get real time events from the server
exec Run a command in a running container
export Export a container's filesystem as a tar archive
history Show the history of an image
images List images
import Import the contents from a tarball to create a filesystem image
info Display system-wide information
inspect Return low-level information on Docker objects
kill Kill one or more running containers
load Load an image from a tar archive or STDIN
login Log in to a Docker registry
logout Log out from a Docker registry
logs Fetch the logs of a container
pause Pause all processes within one or more containers
port List port mappings or a specific mapping for the container
ps List containers
pull Pull an image or a repository from a registry
push Push an image or a repository to a registry
rename Rename a container
restart Restart one or more containers
rm Remove one or more containers
rmi Remove one or more images
run Run a command in a new container
save Save one or more images to a tar archive (streamed to STDOUT by default)
search Search the Docker Hub for images
start Start one or more stopped containers
stats Display a live stream of container(s) resource usage statistics
stop Stop one or more running containers
tag Create a tag TARGET_IMAGE that refers to SOURCE_IMAGE
top Display the running processes of a container
unpause Unpause all processes within one or more containers
update Update configuration of one or more containers
version Show the Docker version information
wait Block until one or more containers stop, then print their exit codes
Run 'docker COMMAND --help' for more information on a command.
现在你有组像经理多个命令container
,image
。当你运行这个组
$ docker image
Usage: docker image COMMAND
Manage images
Options:
--help Print usage
Commands:
build Build an image from a Dockerfile
history Show the history of an image
import Import the contents from a tarball to create a filesystem image
inspect Display detailed information on one or more images
load Load an image from a tar archive or STDIN
ls List images
prune Remove unused images
pull Pull an image or a repository from a registry
push Push an image or a repository to a registry
rm Remove one or more images
save Save one or more images to a tar archive (streamed to STDOUT by default)
tag Create a tag TARGET_IMAGE that refers to SOURCE_IMAGE
因此,作为docker build
是一个别名docker container build
。 Docker最初都是关于一级命令的,后来团队意识到他们需要一种将命令分组的方法,这就是为什么要保持它与旧的客户端兼容的原因
0
Docker以前使用的命令如docker run
和docker build
运行容器或构建映像。在后来的版本中,他们觉得他们应该按照@ tarun-lalwani的建议指定并创建一个组,因此docker run
或docker container run
(它们只是彼此的别名)没有区别。
相关问题
- 1. 在泊坞窗命令行
- 2. 泊坞窗命令失败Cygwin中 - 泊坞窗服务达
- 3. “泊坞窗,撰写”命令来设置泊坞窗,compose.yml文件
- 4. 视窗CMD泊坞窗命令管道
- 5. 泊坞入口点使用泊坞窗运行命令
- 6. 泊坞窗:无法运行命令泊坞
- 7. 泊坞窗 - 击:IP:找不到命令
- 8. 泊坞窗tar命令不工作
- 9. 泊坞窗cp命令不允许
- 10. 泊坞窗运行centos6命令失败
- 11. 泊坞窗 - 编辑“泊坞窗”文件
- 12. 从泊坞窗
- 13. 泊坞窗
- 14. 内泊坞窗
- 15. 在泊坞窗
- 16. 如何运行泊坞窗,构成对泊坞窗群(不含泊坞窗机)
- 17. 泊坞窗机VS泊坞运行
- 18. 泊坞窗:在Dockerfile
- 19. 泊坞窗容器
- 20. 泊坞窗更新
- 21. 泊坞窗拉不kubernetes相关图片
- 22. NPM命令泊坞容器不可
- 23. 泊坞窗:当它已经开始
- 24. 泊坞窗 - 通过argumens与泊坞窗以服务构成了
- 25. 更新泊坞窗,泊坞窗机,码头工人撰写
- 26. 泊坞窗:改变文件夹中存储泊坞窗卷
- 27. 泊坞窗:`码头工人run`和'泊坞窗service`
- 28. 如何在泊坞窗运行线路覆盖CMD命令
- 29. 与环境变量泊坞窗运行命令
- 30. 切割/格式化泊坞窗服务命令