Jonathan Yue Chun

I updated the issue, the sensor problem was because of insufficient default RBAC permission over argo-worflow-sa service account.

this issue can easily be replicated using the gitlab-ci.yml below ```yaml stages: - test variables: DOCKER_TLS_CERTDIR: "" DOCKER_DRIVER: overlay2 stages: - test-cluster test-cluster: image: docker:stable variables: KUBECTL: v1.21.3 stage: test...

@iwilltry42 no problem. Below are the logs ```sh INFO[0000] Prep: Network INFO[0000] Created network 'k3d-metascheduler-1585478' (18a6fca94d647768ec6e24cf2aa72b99e3fce173d06960a6b3876411aaf1fc71) INFO[0000] Created volume 'k3d-metascheduler-1585478-images' INFO[0001] Creating node 'k3d-metascheduler-1585478-server-0' INFO[0010] Deleted 57fd0275f6374f899d2b61473b364cd792f80349d8abef83e0862851e4e10585 INFO[0010] Creating node...

@iwilltry42 any news about it or workaround ?

@iwilltry42 the proposed solution is not to use DinD, which is not possible on my ends...

Hi thanks for the hack, this was what i thought at the beginning, sadly i don't have direct access to the runner itself. How about k3d itself integrate a new...

hi sorry for late reply ! Hmmn, to answer your question. I probably messed up my thinking :(

Hi again, For information, the same bug can easily be reproduced using devcontainers tool from vscode. https://code.visualstudio.com/docs/remote/containers