In this example we will be building a Varnish Cache 6.4.0 from scratch that is not forked from one of our existing images.
Our Cloud Container product is built on top of a technology called Docker that utilises containers to run websites or applications in. These containers each use an 'image' that the container runs, for example your first container may use the Apache + PHP 8.2 image and your next may use the Nginx + PHP 7.4 image.
We provide a few images out of the box, but if you need something we don't provide, that's where custom images come in. They allow you to build an image to your exact specifications and then run containers on your server using that image.
Good question. We have tried to make this product as flexible as possible and hope that you'll be able to build whatever you may need. We already have people using custom images to run Ruby on Rails, unique PHP modules and completely custom web server stacks. It's really up to you.
That's not to say there aren't any limitations, you may find some, but if you do we'll do our best to help you through them.
- Create a custom image. Select the option to not fork from another image.
- Replace your Dockerfile from this example repository.
- Copy the default-data/ from this example repository into your custom image repository. This directory will contain the Supervisord and Varnish config files that you can adjust to your needs.
- Copy the manifest.yml.example to your custom image repository. Update the provider: field to your SiteHost account name.
- Commit the changes.
- Viewing Build Status and Build Log.
To learn more about custom images, please see our knowledge base:
Cloud Container - https://kb.sitehost.nz/cloud-containers
Custom Images - https://kb.sitehost.nz/cloud-containers/custom-images