blob: 0897bb183e526614196f8c717858e9a807e03041 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
|
---
stage: Verify
group: Continuous Integration
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
comments: false
type: index
---
# Docker integration
There are two primary ways to incorporate [Docker](https://www.docker.com) in your CI/CD workflow.
- **[Run your CI/CD jobs](using_docker_images.md) in Docker containers.**
You can create CI/CD jobs to do things like test, build, or publish
an application. These jobs can run in Docker containers.
For example, you can tell GitLab CI/CD to use a Node image that's hosted on Docker Hub
or in the GitLab Container Registry. Your job then runs in a container that's based on the image.
The container has all the Node dependencies you need to build your app.
- **Use [Docker](using_docker_build.md) or [kaniko](using_kaniko.md) to build Docker images.**
You can create CI/CD jobs to build Docker images and publish
them to a container registry.
|
