Managing Containers
Prerequisites
Starting Containers
The previous steps covered the process from adding a provider to deploying the container. This step will focus on managing containers, which includes both standard containers and environment service containers.
To resume from the previous step, navigate to the desired environment by clicking Environments on the main left-hand navigation and selecting the appropriate environment.
This will navigate to the environment dashboard. In the upper right corner, there are buttons that say Start All and Stop All. These buttons can start or stop all containers in the environment.
For starting a container individually, click on the Containers tab and then select the container created in the previous section. In the container modal, there are similar buttons in the upper right corner, but these are scoped to the container itself.
Use the Start All button from the environment dashboard to start all the containers in the environment. The containers that should start at this point are:
- Discovery
- The container created in the previous section.
The containers that should not start at this point are:
- Load Balancer
- VPN
Once the containers have started, open the container and navigate to the Instances tab. This tab is where the Instance Console is located, which shows all output from the container's main process.
Configuring Containers
In the left-side navigation in the Container Modal, select the Config tab. In this section, there are options to configure network, runtime, deployment, resources, and auto-scaling.
The first section, network, is a common place for users to pay attention early. In the next section Taking A Container Public network settings will be discussed in more detail.
Volumes
Volumes are a way to persist data across container restarts. This is a common need for databases, file storage, and other services that need to maintain state. Volumes are outside of this guide but for more information about volumes check out the main reference.
Backups
Backups are a two-part configuration. Currently, Cycle supports an integration with Backblaze.
Settings
The settings tab allows the user to: