---
title: Manage Containers
slug: manufacturing-connect-edge-v1/manage-containers
docTags: 
createdAt: 2022-09-23T14:47:00.000Z
---

You can run and manage containers by navigating to **Applications&#x20;**>**&#x20;Containers**.&#x20;

# Run a Container

You can add and run a container locally using the *Run&#x20;*&#x63;ommand. The named container pulls the container from the Docker registry and it appears on the Container pane, running locally.

Manufacturing Connect Edge supports Docker Registry v2.

## Before You Begin

- You must do one of the following:
  - [Create a Docker Image to Deploy to Your Private Repository](docId\:cK7Qq25fb-mrZB8pPIKt1)&#x20;
  - [Upload an Image](docId\:mZVA3StBZvAqaSjA2uceS) into Manufacturing Connect Edge&#x20;
  - [Download an Image](docId\:g0Fob8SG_zyedWaNCoEnI)&#x20;
- You must also [Add a Registry](docId:_FH5SltUMHhZ42AhbXaGY) entry.

**To run a container:**

1. Navigate to **Applications&#x20;**> **Containers**.&#x20;
2. From the *Containers* pane, click **Run**.&#x20;
   The *Enter command to run&#x20;*&#x66;ield appears.&#x20;
   ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/BGThJUH-V8XvEb9nLjAMX_runcontainer.png" size="80" width="1344" height="581" caption="Container Run button" position="center" showCaption="true"}
3. Enter the docker run command for the selected application, and then click **Run**.

:::hint{type="info"}
**Example**: `docker run -d --name hello hello-world`
:::

The named container appears in the *Containers&#x20;*&#x70;ane, and its state is running. The container runs locally.

# Manage individual containers

Refer to the image and callouts below for management options for containers.&#x20;

![](https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/ElAiOSYbgq0ZXGE6JY1f0_image.png "Management options for containers")

\[1] **Copy port number**

\[2] **Start and Stop container**: Once stopped, the container shows an *Exited&#x20;*&#x73;tatus.&#x20;

\[3] **Pause and Un-pause container**

\[4] **Remove container**: The container is removed from the Containers pane.&#x20;

\[5] **Show container log**: This is similar to the logs available from the Overview pane but displays directly from the container environment. See the "View Container Logs" section below for more information.&#x20;

\[6] **Inspect**: Displays the configuration, attached volumes, and policies included in the container. From the specified container pane, you can reload the container.

\[7] **Terminal**: You can open a terminal console for a specified container. The terminal is normally used for diagnostic purposes. It allows you to modify the application's configuration, though this is not recommended.

\[8\[ **Container top**: You can view information about the container services that are running. This is normally used by developers.

# View Container Logs

When you click the **Show container log** icon, the *Log* pane displays.&#x20;

Refer to the image and callouts below for filter options for container logs.&#x20;

![](https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/WwS2IsESQc3GVaP1OJEPj_image.png)

\[1] **Search**: Enter search terms to find text in all the log entries defined.&#x20;

\[2] **Fetch Log**: You can review a log for the specified time period you select (All logs, Last day, Last 4 hours, Last hour, or Last 10 minutes, Last minute).&#x20;

\[3] **Line Wrap**: If enabled, text is formatted to fit within the screen, so no horizontal scrolling in the log screen is needed.&#x20;

\[4] **Display Timestamp**: If enabled, the timestamp for each message is displayed.&#x20;

\[5] **Download Logs**: Select to download all logs or only logs you've filtered to display.&#x20;

