Assertion: container | /r/HasProperty | started
Facets:
value: from the same image
type: OTHER
value: from that
type: OTHER
Source sentences:
text: This allows containers to be started and stopped as needed, to flex up at a time of peak demand, and to flex down when not needed.
text: Containers can be started, stopped, committed and terminated.
text: This allows containers to be started and stopped as needed, to flex up at a time of peak demand, and to flex down when not needed.
text: When the container is started, the image layers are mounted read-only with a kernel namespace.
text: This allows containers to be started and stopped as needed, to flex up at a time of peak demand, and to flex down when not needed.
text: The ADDDB copies databases (Primary, Secondary, and Log files) into a container, and are attached when the container is started and detached when stopped.
text: Using MOUNTDB databases are mounted and attached when the container is started, and unmounted and detached when stopped.
text: In this example, the Adventureworks database is copied into the container, and attached when the container is started.
text: When starting a container, the image that the container is started from is mounted read-only.
text: The read-only layers of an image can be shared between any container that is started from the same image, whereas the “writable” layer is unique per container (because: you don’t want changes made in container “a” to appear in container