runner image to use ansible with Woodpecker
  • Dockerfile 100%
Find a file
thomas.laerm 45d211fa5d
All checks were successful
ci/woodpecker/push/build Pipeline was successful
added README.md
2025-12-22 10:57:17 +01:00
.woodpecker Update .woodpecker/build.yaml 2025-11-01 15:06:46 +00:00
.gitignore added README.md 2025-12-22 10:57:17 +01:00
Dockerfile add python kubernetes package 2025-11-30 20:48:46 +01:00
README.md added README.md 2025-12-22 10:57:17 +01:00

Ansible Runner Image

This repository contains the configuration for building a runner image used in my Ansible CI/CD pipelines.

Overview

The runner image is built using the Woodpecker CI docker-buildx plugin and is designed to be used in automated build pipelines. It's configured to automatically tag images with the latest tag and push them to our internal Forgejo registry.

Build Process

The image is automatically built and pushed when changes are pushed to the master branch. The build process uses the following configuration:

  • Registry: git.lukko.de
  • Repository: ${CI_REPO_OWNER}/${CI_REPO_NAME}
  • Tags: latest
  • Build Arguments:
    • CI_SYSTEM_VERSION=${CI_SYSTEM_VERSION}
    • CI_SYSTEM_VERSION=${CI_SYSTEM_VERSION}

Usage

This image is intended to be used as part of a CI/CD pipeline. It should be referenced by other pipeline steps that require a runner environment.

Configuration

The build process uses the following environment variables:

  • CI_REPO_OWNER: The repository owner name (automatically provided by Woodpecker)
  • CI_SYSTEM_VERSION: System version identifier (passed as build argument)
  • DOCKER_TOKEN_RW: Docker registry authentication token (from secrets)

Docker Registry

The built image is pushed to our internal Forgejo package registry at git.lukko.de.

Development

To build locally, you can use:

docker build -t <your-registry-server>/${CI_REPO_OWNER}/${CI_REPO_NAME}:latest .

Note: You'll need appropriate credentials for the docker registry.