Skip to content

Windows cloud-init configuration #ps1_sysnative #587

@hulto

Description

@hulto

Problem

I'm working on adding Windows runners to my garm deployment and it seems like the install_wrapper is missing #ps1_sysnative.
I wrote my own provider for harvester but don't think that should affect the cloud init config that's pulled from the server.
Should i be inserting the #ps1_sysnative directive as apart of my provider?

$ErrorActionPreference="Stop"

Trouble shooting

Garm is able to provision the VMs and set the cloud-init data.
Cloud init fails to execute the script.

If I stop the VMs before they start for the first time and update the user-data with #ps1_sysnative at the top the VMs execute the script and install the act runner correctly.

My Environment:

  • gitea
  • runners are built using a modified version of the github runner-images to support harvester
  • hypervisor - harvester
  • garm provider is a custom to work with harvester.
  • garm build using a base of ghcr.io/cloudbase/garm:nightly@sha256:acd527ab90448e1b72b639b201ace7af27e8fcb49384c094dadd1aa6e1ac4f58

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions