Docker Backend: fully support windows container

[6543]

close #4286 address one bug described in https://github.com/woodpecker-ci/woodpecker/issues/4274

TODO: actuall testing of:

• [x] normal steps
• [x] services
• [x] plugins

[codecov[bot]]

Codecov Report

Attention: Patch coverage is 90.00000% with 3 lines in your changes missing coverage. Please review.

Project coverage is 27.64%. Comparing base (5c22047) to head (35c7fe9). Report is 25 commits behind head on main.

Files with missing lines	Patch %	Lines
pipeline/backend/docker/convert_win.go	88.46%	2 Missing and 1 partial :warning:

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #4381 +/- ## ========================================== + Coverage 27.58% 27.64% +0.06% ========================================== Files 382 383 +1 Lines 27922 27950 +28 ========================================== + Hits 7703 7728 +25 - Misses 19532 19534 +2 - Partials 687 688 +1 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[6543]

 ./dist/woodpecker-agent.exe --backend-engine docker --backend-docker-host "npipe:////./pipe/docker_engine"

[6543]

look's like it works :)

the only thing is i had to modify the clone plugin:

--- a/plugins/plugin-git/Dockerfile.Windows
+++ b/plugins/plugin-git/Dockerfile.Windows
@@ -1,7 +1,7 @@
 # syntax = docker/dockerfile:1
 # escape=`

-FROM mcr.microsoft.com/windows/servercore:ltsc2022
+FROM mcr.microsoft.com/windows/servercore:1809

 # Busybox Unicode https://github.com/rmyorston/busybox-w32

[6543]

so yes woodpecker itselve wont support windows container fully ... ... mostly depending on:

• https://github.com/woodpecker-ci/autoscaler/issues/202
• https://github.com/woodpecker-ci/autoscaler/issues/133 (we need to autoscale a windows host with docker configured to host windows container ...)

[6543]

PS: I still have no idea why some things work and some are incompatible :/

[6543]

my test config: .woodpecker/check.yaml:

labels:
  backend: docker
  platform: windows/amd64

skip_clone: true

depends_on:
    - echo

steps:
    check_echo:
        image: mcr.microsoft.com/windows/servercore:1809
        commands:
            - echo some checks
            - sleep 2s

.woodpecker/echo.yaml:

labels:
  backend: docker
  platform: windows/amd64

when:
  - event: pull_request
  - event: [push, deployment]
    branch:
      - ${CI_REPO_DEFAULT_BRANCH}

clone:
  clone:
    image: woodpecker-windows-git

steps:
    createFile:
        image: mcr.microsoft.com/windows/servercore:1809
        commands:
            - echo FROM alpine:edge >> Dockerfile
            - echo RUN apk update >> Dockerfile

    echo:
        image: mcr.microsoft.com/windows/servercore:1809
        commands:
            - echo buildZ
            - sleep 10s
            - ls
    depl:
        image: bash
        commands: echo deploy
        when:
            - event: deployment
              branch: ${CI_REPO_DEFAULT_BRANCH}

[6543]

[6543]

@cduchenoy :point_up: ...?

[cduchenoy]

Hi,

It's excellent!

On Windows, we must take the tag which corresponds to the kernel version

see https://hub.docker.com/r/microsoft/windows-servercore

So I think I should check :)

• 1809 => Windows server 2016 base
• ltsc2019 => Windows server 2019 base
• ltsc2022 => Windows server 2022 base
• ltsc2025 => Windows server 2025 base

did you also test the agent build?

https://github.com/GECO-IT/woodpecker-windows/blob/main/agent/backend-docker/Dockerfile.Windows

[cduchenoy]

For test a service image, you can use as a base: https://github.com/GECO-IT/woodpecker-windows/blob/main/base/windows-base/Dockerfile.base-chocolatey.Windows

Base image are in docker-hub: https://hub.docker.com/r/gecoit84/woodpecker-windows-base-chocolatey

and add:

choco install mysql

I haven't tried so I don't know if it launches the service correctly

[6543]

did you also test the agent build?

no as I only wana test if the engine works ... so the deployment of the agent should not alter the test ...

[6543]

For test a service

ah nice ... will do so

[6543]

labels:
  backend: docker
  platform: windows/amd64

skip_clone: true

steps:
    create:
        image: mcr.microsoft.com/windows/servercore:1809
        commands:
            - echo some checks > NEW
            - sleep 2s

    curl:
        image: a6543/woodpecker-windows-base-chocolatey:latest
        commands:
            - choco install -y curl
            - curl.exe -I http://caddy:80
            - curl.exe http://caddy:80/NEW

services:
    caddy:
        image: a6543/woodpecker-windows-caddy-static:latest
        ports:
            - 80

services work just fine ...