The job below first builds and then publishes an image defined in.

For example, if your company uses Space On-Premises and doesn't allow using self-hosted workers. The main reason of using job.kaniko over host.dockerBuildPush is when using of the latter is not possible. Technically, this is a job.container step that runs in a container based on a special image. Job.kaniko lets you run Docker builds in a container with the pre-installed Kaniko tool. Some things might work differently with Kaniko compared to classic Docker. In case of job.kaniko, you must build image artifacts in a separate step and provide them to job.kaniko via the file share. It's easier and faster to build image dependencies – As you can pre-install all necessary tools to the host machine, the same host step can be used not only to build and publish an image but also to build artifacts required for this image. It's possible to build Windows Docker images (if the host machine runs on Windows). Technically, this is a DSL wrapper for the block that runs the docker build and docker push commands. lets you run Docker builds on a self-hosted or Space Cloud worker. Publishing an image to an external repository, for example, Docker Hub.Īutomation provides two different ways for building and publishing Docker images depending on a run environment: Learn more about worker poolsĪutomated Docker builds: All image dependencies already exist and all you need is to build and publish a Docker image to Space Packages.Ĭreating dependencies before the build: An Automation job must create image dependencies before building and publishing the image. If you want to run a job on a Space Cloud worker, ensure that the Space Automation Cloud pool is used. If you want to run a job on a self-hosted worker, ensure it has Docker installed. A Dockerfile that defines the Docker image is stored in the project sources.

Download jetbrains space docker