![]() Removes the network at the end of the job.Connects the service and containers to the bridge network.Creates a bridge network, similar to the Docker command docker network create.How the runner creates a network for each job The runner uses the build alias to resolve the job container. To enable IPv6 support, set enable_ipv6 to true in the Docker configuration.įor more information, see the Docker documentation. This feature works only when the Docker daemon is configured with IPv6 enabled. To set the default Docker address pool, use default-address-pool inĪre already used in the network, Docker networks may conflict with other networks on the host, ] (.) executor = "docker" FF_NETWORK_PER_BUILD = true gitlab-ci.ymlĭefine an image that the runner uses for all jobs and a list of For more information about types of services, see Services.ĭefine images and services in. services: The additional image that creates another container and links to the image.To define the image version, use a colon ( :) to add a tag.For more information, see the Docker documentation. Enter an image from the local Docker Engine, or any image inĭocker Hub.image: The name of the Docker image that the runner uses to run jobs.To configure the Docker executor, you define the Docker images and services in. The image where your job runs must have a working shell in its operating system PATH.The Docker executor supports the following configurations.įor known issues and additional requirements of Windows configurations, see Use Windows containers.Ĭoncurrent = 4 ] name = "myRunner" url = "" token = "." executor = "docker" tls_verify = true image = "my.registry.tld:5000/alpine:latest" privileged = false disable_entrypoint_overwrite = false oom_kill_disable = false disable_cache = false volumes = shm_size = 0 allowed_pull_policies = allowed_images = allowed_services = "size" = "50G" Configure images and services Post-job: Create cache, upload artifacts to GitLab.Job: Runs your build in the Docker image you configure for the runner.Prepare: Creates and starts the services.The Docker executor divides the job into several steps: The special Docker image, see the GitLab Runner repository. ![]() The Docker executor uses a special Docker image based on Alpine Linux thatĬontains the tools to run the prepare, pre-job, and post-job steps. The configurations you define in config.toml.To connect to Docker Engine, the executor uses: To run each job in a separate and isolated container. Use the same image to test commands locally without the requirement of running a job in the CI server.Maintain the same build environment for each job.GitLab Runner uses the Docker executor to run jobs on Docker images. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |