Docker/Current/Troubleshooting/Running Containers - Revision history

WikiSysop at 09:30, December 3, 2024

2024-12-03T09:30:29Z

WikiSysop: Text replacement - "\|Platform=([^\|])GenesysEngage-onpremises([\|])" to "|Platform=$1GenesysEngage-cloud$2"

2020-07-25T02:32:33Z

Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "\|Platforms?=([^\|])PureCloud([\|])" to "|Platform=$1GenesysCloud$2"

2020-07-15T11:59:36Z

Text replacement - "\|Platforms?=([^\|]*)PureCloud([\|]*)" to "|Platform=$1GenesysCloud$2"

WikiSysop: Text replacement - "\|Platforms?=([^\|])PureEngage([\|])" to "|Platform=$1GenesysEngage-onpremises$2"

2020-07-15T11:51:13Z

Text replacement - "\|Platforms?=([^\|]*)PureEngage([\|]*)" to "|Platform=$1GenesysEngage-onpremises$2"

Xavier: Published

2020-06-16T15:24:07Z

Published

WikiSysop at 13:36, January 17, 2020

2020-01-17T13:36:15Z

Jaba: Published

2019-02-25T07:05:15Z

Published

New page

{{Article
|Standalone=No
|DisplayName=Running Containers
|Platform=PureEngage, PureConnect, PureCloud
|Context=Instructions to run the Docker containers.
|Section={{Section
|sectionHeading=Running Containers
|Type=Unstructured
|freetext=Containers are running instances of an Image. To run containers, follow these steps:
# Create a container from the base image for the latest version of the Ubuntu that is available.
#: {{NoteFormat|
#*If you do not have an Ubuntu base image installed locally, extract the latest one for your local repository.
#*You must start the container in interactive mode attached to the current terminal and running the bash shell.
#*After running, make sure you shut down the container by running 'exit'.|<style (optional)>}} [[File:code-1.JPG|900px|none|middle|frameless]]
# Run the appropriate Docker command to obtain the name of the previously run container. Issue the appropriate command to restart the container for which you obtained the name. Do NOT create a new container. Restart the container that was just used. [[File:Code2.JPG|900px|none|middle|frameless]]
# Stop the container, and then remove the container from the system by using the following command.[[File:Code3.JPG|900px|none|middle|frameless]]
# Create (not run) a container called "my_container" by using the parameters that will allow the container to run interactively, and get the terminal attached to the local console running the bash shell. Ensure the container is not running.[[File:Code4.JPG|900px|none|middle|frameless]]
# Start the container, and ensure the container is running. Run the following command to attach your session to the running container to ensure you are logged on to the shell.[[File:Code5.JPG|900px|none|middle|frameless]]
}}{{Section
|sectionHeading=Lifecycle
|Type=Unstructured
|freetext=The following commands illustrate the Docker Lifecycle:
* <code>docker create</code> creates a container but does not start the container.
* <code>docker rename</code> allows the container to be renamed.
* <code>docker run</code> creates and starts a container in a single operation.
* <code>docker rm</code> deletes a container.
* <code>docker update</code> updates a container's resource limits.

Usually, when you run a container without options, it will start and stop immediately. If you want the container to keep running, you can use the command, <code>docker run -td container_ID</code>. This command uses the option<code>-t </code>to allocate a pseudo-TTY session and option<code>-d </code>to detach the container automatically (you can run container in background and print the container ID).

To have a transient container, use the command <code>docker run –rm</code>. This command will remove the container after it stops.

To map a directory on the host to a docker container, use the command <code>docker run -v $HOSTDIR:$DOCKERDIR<</code>.

To remove the volumes associated with the container, the deletion of the container must include the option<code>-vswitch</code> like in <code>docker rm -v</code>.

There is also a logging driver available for individual containers in docker 1.10. To run docker with a custom log driver (that is syslog), use the command <code>docker run --log-driver=syslog.</code>

<code>docker run --name yourname docker_image</code> is a useful command because when you specify <code>--name</code> inside the run command, you can start and stop a container by calling it with the name that you specified when you created it.
}}{{Section
|sectionHeading=Starting and Stopping a Container
|Type=Unstructured
|freetext=Commands to start and stop a container:
* <code>docker start</code> starts a container so it is running.
* <code>docker stop</code> stops a running container.
* <code>docker restart</code> stops and starts a container.
* <code>docker pause</code> pauses a running container, "freezing" it in place.
* <code>docker unpause</code> unpauses a running container.
* <code>docker wait</code> blocks until running container stops.
* <code>docker kill</code> sends a SIGKILL signal to a running container.
* <code>docker attach</code> connects to a running container.

To integrate a container with a host process manager, start the daemon with the commands <code>-r=false</code> and then use <code>docker start -a</code>.
}}
}}

@@ Line 2: / Line 2: @@
 |Standalone=No
 |DisplayName=Running Containers
-|Platform=GenesysEngage-onpremises, PureConnect, GenesysCloud
+|Platform=GenesysEngage-cloud, PureConnect, GenesysCloud
 |ComingSoon=No
 |Context=Instructions to run the Docker containers.

@@ Line 2: / Line 2: @@
 |Standalone=No
 |DisplayName=Running Containers
-|Platform=GenesysEngage-onpremises, PureConnect, PureCloud
+|Platform=GenesysEngage-onpremises, PureConnect, GenesysCloud
 |ComingSoon=No
 |Context=Instructions to run the Docker containers.

@@ Line 2: / Line 2: @@
 |Standalone=No
 |DisplayName=Running Containers
-|Platform=GenesysEngage-cloud, PureConnect, GenesysCloud
+|Context=Instructions to run the Docker containers.
 |ComingSoon=No
-|Context=Instructions to run the Docker containers.
+|Platform=PureConnect, GenesysCloud, GenesysEngage-cloud
 |Section={{Section
 |sectionHeading=Running Containers
 |alignment=Vertical
 |structuredtext={{{!}} class="wikitable"
@@ Line 17: / Line 21: @@
 Containers are running instances of an Image. To run containers, follow these steps:
 # Create a container from the base image for the latest version of the Ubuntu that is available.
 #: {{NoteFormat|
 #*If you do not have an Ubuntu base image installed locally, extract the latest one for your local repository.
 #*You must start the container in interactive mode attached to the current terminal and running the bash shell.
 #*After running, make sure you shut down the container by running 'exit'.|<style (optional)>}} [[File:code-1.JPG|900px|none|middle|frameless]] <br />
-# Run the appropriate Docker command to obtain the name of the previously run container. Issue the appropriate command to restart the container for which you obtained the name. Do NOT create a new container. Restart the container that was just used. [[File:Code2.JPG|900px|none|middle|frameless]]
+#Run the appropriate Docker command to obtain the name of the previously run container. Issue the appropriate command to restart the container for which you obtained the name. Do NOT create a new container. Restart the container that was just used. [[File:Code2.JPG|900px|none|frameless]]
-# Stop the container, and then remove the container from the system by using the following command.[[File:Code3.JPG|900px|none|middle|frameless]]
+#Stop the container, and then remove the container from the system by using the following command.[[File:Code3.JPG|900px|none|frameless]]
-# Create (not run) a container called "my_container" by using the parameters that will allow the container to run interactively, and get the terminal attached to the local console running the bash shell. Ensure the container is not running.[[File:Code4.JPG|900px|none|middle|frameless]]
+#Create (not run) a container called "my_container" by using the parameters that will allow the container to run interactively, and get the terminal attached to the local console running the bash shell. Ensure the container is not running.[[File:Code4.JPG|900px|none|frameless]]
-# Start the container, and ensure the container is running. Run the following command to attach your session to the running container to ensure you are logged on to the shell.[[File:Code5.JPG|900px|none|middle|frameless]]
+#Start the container, and ensure the container is running. Run the following command to attach your session to the running container to ensure you are logged on to the shell.[[File:Code5.JPG|900px|none|frameless]]
 |Status=No
 }}{{Section
 |sectionHeading=Lifecycle
 |alignment=Vertical
 |structuredtext=The following commands illustrate the Docker Lifecycle:
 * <code>docker create</code> creates a container but does not start the container.
-* <code>docker rename</code> allows the container to be renamed.
+*<code>docker create</code> creates a container but does not start the container.
-* <code>docker run</code> creates and starts a container in a single operation.
+*<code>docker rename</code> allows the container to be renamed.
-* <code>docker rm</code> deletes a container.
+*<code>docker run</code> creates and starts a container in a single operation.
-* <code>docker update</code> updates a container's resource limits.
+*<code>docker rm</code> deletes a container.
 Usually, when you run a container without options, it will start and stop immediately. If you want the container to keep running, you can use the command, <code>docker run -td container_ID</code>. This command uses the option<code>-t </code>to allocate a pseudo-TTY session and option<code>-d </code>to detach the container automatically (you can run container in background and print the container ID).
@@ Line 53: / Line 57: @@
 }}{{Section
 |sectionHeading=Starting and Stopping a Container
 |alignment=Vertical
 |structuredtext=Commands to start and stop a container:
 * <code>docker start</code> starts a container so it is running.
-* <code>docker stop</code> stops a running container.
+*<code>docker start</code> starts a container so it is running.
-* <code>docker restart</code> stops and starts a container.
+*<code>docker stop</code> stops a running container.
-* <code>docker pause</code> pauses a running container, "freezing" it in place.
+*<code>docker restart</code> stops and starts a container.
-* <code>docker unpause</code> unpauses a running container.
+*<code>docker pause</code> pauses a running container, "freezing" it in place.
-* <code>docker wait</code> blocks until running container stops.
+*<code>docker unpause</code> unpauses a running container.
-* <code>docker kill</code> sends a SIGKILL signal to a running container.
+*<code>docker wait</code> blocks until running container stops.
-* <code>docker attach</code>  connects to a running container.
+*<code>docker kill</code> sends a SIGKILL signal to a running container.
 To integrate a container with a host process manager, start the daemon with the commands <code>-r=false</code> and then use <code>docker start -a</code>.