| `stage` | build | CI Component Input | The CI Stage to run the component in. |
| `KANIKO_CONTAINER_TAG` | `v1.23.0-debug` | CI Component Input | MUST be a debug container to have the required shell for GitLab CI. |
| `KANIKO_DOCKERFILE` | `Dockerfile` | CI Component Input | Override if Dockerfile is not in the root of the project. |
| `KANIKO_REGISTRIES` | `github` | CI Component Input | Any combination of 'gitlab,dockerhub'. |
| `KANIKO_COMP_DISABLED` | `` | CI Variable | Set to 'true' to disable. Useful when this is an component included in another component. |
| `KANIKO_DOCKERFILE` | `Dockerfile` | CI Variable | Override: if Dockerfile has another pathname or to repeatedly use component to build many dockerfiles in a project. |
| `CI_COMPONENT_DEBUG` | `` | CI Variable | Set to 'true' to see more verbose component output. GitLabs standard CI_DEBUG_TRACE=true also triggers this trace. |
Note: KANIKO_DOCKERFILE must be a CI variable in order for the component to be called multiple times. Component Inputs only allow one value per include.
#### Dockerhub
If you are deploying to dockerhub, you must also set these variables and be sure to use the scope indicated.
When pushing to the projects GitLab registry, all these variables are automatically set.
...
...
@@ -45,9 +47,9 @@ You can also use the example dockerhub job in this component to extend the compo