How to build your own Custom AMI
On hosted installations of CircleCI, the AMI used for VM Service, which provides access to a dedicated Docker daemon via the
machine executor (see Executor Types: Using Machine) and
setup_remote_docker (see Running Docker Commands: Overview), is completely customizable.
By extending our default installed set of packages and dependencies to create your own custom VM Service AMI, you can install custom versions of Docker, as well as pre-bake any common frameworks, security tools, proxy settings, etc., into the AMI itself, simplifying the required setup and configuration steps that might otherwise have to live in the config.yml configuration files for any projects with jobs that require the
machine executor or
CircleCI Server 3.x/4.x
To build the image, you can utilize our open-source circleci-server-linux-image-builder.
Once the image is built, you can customize the Server 4.x's Helm
values.yml to include the image build like so:
# for AWS
# for GCP
Once the image is built, you can add the AMI ID via the KOTS Admin Console.
- [Server] Clearing the Nomad job queue
- [Server] How to restart the Replicated services
- How to start the KOTS Admin Console
- How to manage pods