Container Configuration Overview

Learning the container configuration form is an essential piece of becoming a Cycle power user.

This form is broken down into the following sections, each of which has their own corresponding page.

  1. Network
  2. Runtime
  3. Deployment
  4. Resources
  5. Auto-Scaling
  6. Integrations

Changing configuration restarts container

When saving changes to the container configuration, the platform will have to restart the container to set those changes into effect. This process requires a container restart.

Container instances restarted during a container restart event are subject to update policies for more granular control.

Container Configuration and Instances

Containers and Instances are managed as a single unit. This means that the container level configuration is applied to all instances of that container. There is no mutability between instances when it comes to the config.

Nuance

Theoretically a user could prove the above statement incorrect by changing the data returned by fields who's values are derived from a URL http call's return data.

Updating the container configuration applies those changes to each individual instance. At this time, if a user would like to have instances that are configured differently using the same container, making multiple containers with different configurations is the suggested approach.