container.options not being passed to container on self-hosted ARC

[anitabee]

Hi,

we are running ARC scale sets with Kubernetes mode. And while trying to spin up container over the GitHub Actions we noticed that container.options are not passed to container, at least it looks like this is an issue.

Running workflow on ARC

Below example run returns root user, however user with UID 1000 exist on image.

on:
  push:
    branches: [ main ]
jobs:
  container-test-job:
    runs-on: self-hosted-runnerscaleset
    container:
      image: node:18
      env:
        NODE_ENV: development
      ports:
        - 80
      volumes:
        - my_docker_volume:/volume_mount
      options: --cpus 1 --user 1000:1000
    steps:
      - name: Check for dockerenv file
        run: |
          whoami
          cat /etc/passwd

Output of whoami:
root

Output of cat /etc/passwd:

root:x:0:0:root:/root:/bin/bash
...
node:x:1000:1000::/home/node:/bin/bash

Running workflow on GitHub hosted runner

Running same workflow on GitHub hosted runner so runs-on: ubuntu-latest works as expected.

Output of whoami:

node

Output of cat /etc/passwd is same as on ARC.

Question

I understand that GitHub hosted runner is totally different setup but I would still expect interface container.options to be able to pass container options in the same way.

Am I getting the whole thing wrong and this is not the way to use it?

Thanks in advance

[anitabee]

Colleague of mine pointed out today that this is not supported https://github.com/actions/runner-container-hooks/blob/main/packages/k8s/README.md#limitations