Custom Installer Image
You can specify a custom installer image to deploy your Development Environments. Use this if you want to use tools, frameworks, or custom configurations not included in the default installer image.
Requirements
To use the Custom Installer Image feature, you first need to create your own Docker image, and push it to a registry that can be accessed by your Okteto instance.
Defining the Custom Image
When creating your image, we recommend extending the image from the latest version of the default pipeline runner image.
Your image can include anything that you need when deploying Development Environments for your organization. The example below shows you how to include wget
:
FROM okteto/pipeline-runner:1.27.0
RUN apt-get upgrade && apt-get install wget
Build and Publish the Custom Image
Once the image has been defined, build it and push it to your container registry.
docker build -t REGISTRY/REPOSITORY:TAG
docker push REGISTRY/REPOSITORY:TAG
Configure your Custom Image
- Self-Hosted
- SaaS
To enable the custom image, update your Okteto Helm configuration file with the following values, and run a helm upgrade to apply the new configuration.
installer:
runner:
registry: REGISTRY
repository: REPOSITORY
tag: TAG
If your instance is hosted by Okteto, contact support to configure your custom image in your Okteto Instance.
Using the Custom Image
Once the configuration has been applied, all the Development Environments will be deployed using your custom image. In order to help you troubleshoot any issues, the name of the image used during deployment is included in the pipeline logs. You can consult this in the Okteto UI.