Why docker API points create an exec and start an exec, cannot be performed at a time-CodePudding

Home > other > Why docker API points create an exec and start an exec, cannot be performed at a time

Why docker API points create an exec and start an exec, cannot be performed at a time

Time：09-17

 To exec a command in a container, you first need To create an exec instance, then start it.

As this is the official document, I can think of a time

1. The command cache, next time can directly use the
2. Create command I give you, the next time you start can directly get the results
3. What do a statistical

Why can't the is on at a time?

But these are only I can reach the edge of thinking, docker excuse me why do it? Or should I through what way to get my answer

Page link：https//www.codepudding.com/other/5220.html

Prev:How to introduce others to DNS

Next:Using URLOS covenant-lite quickstart docker container application development

Tags：

Docker

Links：
CodePudding