Gitea release plugin on windows 2019

johanvdw · May 28, 2021, 2:04pm

When running this plugin we get this error:

 docker run --rm  plugins/gitea-release:1.0-windows-amd64
docker: Error response from daemon: hcsshim::CreateComputeSystem 44984ffc41fb3fe04fe8de525469a9cc02e4267aa8de82bec904fce
2b5b23d63: The container operating system does not match the host operating system.

Also when specifying a specific tag:

docker run --rm  plugins/gitea-release:1.0-windows-amd64
docker: Error response from daemon: hcsshim::CreateComputeSystem 44984ffc41fb3fe04fe8de525469a9cc02e4267aa8de82bec904fce
2b5b23d63: The container operating system does not match the host operating system.

The strange thing is: this has worked before, perhaps docker was updated on our server?

bradrydzewski · May 28, 2021, 2:17pm

plugins need to be explicitly compiled and published for windows. to my knowledge, the gitea release plugin has never been published on windows. If you look at the .drone.yml for this plugin you will see there is no windows pipeline, and there have not been any changes to this plugin for quite some time.

johanvdw · May 28, 2021, 2:36pm

The windows builds are in a different file:

github.com

drone-plugins/drone-gitea-release/blob/master/.drone.windows.yml

---
kind: pipeline
name: testing

platform:
  os: windows
  arch: amd64
  version: 1803

steps:
- name: vet
  pull: always
  image: golang:1.13-windowsservercore-1803
  commands:
  - go vet ./...
  environment:
    GO111MODULE: on
  volumes:
  - name: gopath
    path: C:\\gopath

This file has been truncated. show original

Also this plugin has been working at least until 2 months ago on the same server.

johanvdw · May 28, 2021, 2:57pm

Also this plugin has been working at least until 2 months ago on the same server.

This was a misconception - it looks like the other pipeline build the file on windows, stored it using rsync and then released it from linux.

bradrydzewski · May 28, 2021, 5:21pm

The .drone.windows.yml file was never used, at least not officially (drone can only use a single yaml). It looks like one of our community maintainers must have manually built and pushed a windows image, on his own infrastructure.