actions-runner-dind-rootless image not built for runner version 2.317.0

Abierto
#3,586 5 comentarios 6 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
docker, github-actions, kubernetes

Línea de trabajo

Comienza con la ejecución de release de GitHub Actions enlazada y compara su compilación fallida de rootless-image con la compilación correcta de actions-runner-dind. Comprueba las etiquetas de Docker Hub para ambas variantes de Ubuntu e identifica por qué no se publicó la versión del runner 2.317.0. Se considera terminado cuando haya imágenes rootless correspondientes disponibles para ubuntu-20.04 y ubuntu-22.04.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug community
Checks
Controller Version

v0.27.6

Helm Chart Version

No response

CertManager Version

No response

Deployment Method

Helm

cert-manager installation

N/A

Checks
  • This isn't a question or user support case (For Q&A and community support, go to Discussions. It might also be a good idea to contract with any of contributors and maintainers if your business is so critical and therefore you need priority support
  • I've read releasenotes before submitting this issue and I'm sure it's not due to any recently-introduced backward-incompatible changes
  • My actions-runner-controller version (v0.x.y) does support the feature
  • I've already upgraded ARC (including the CRDs, see charts/actions-runner-controller/docs/UPGRADING.md for details) to the latest and it didn't fix the issue
  • I've migrated to the workflow job webhook event (if you using webhook driven scaling)
Resource Definitions
apiVersion: actions.summerwind.dev/v1alpha1
kind: RunnerDeployment
metadata:
  creationTimestamp: "2023-08-31T16:13:22Z"
  generation: 9276
  name: gh-terraform-secure
  namespace: actions-runner-system
  resourceVersion: "137974423"
  uid: 6a78ee69-9a07-4ac6-9d7d-3b93dfe195fe
spec:
  effectiveTime: "2024-06-10T13:03:25Z"
  replicas: 0
  selector: null
  template:
    metadata:
      annotations:
        ad.datadoghq.com/tags: '{"gha_runner_type": "gh-terraform-secure"}'
      labels:
        app.kubernetes.io/name: gh-terraform-secure
    spec:
      dockerdContainerResources: {}
      env:
      - name: DISABLE_RUNNER_UPDATE
        value: "false"
      - name: DISABLE_WAIT_FOR_DOCKER
        value: "true"
      ephemeral: true
      image: xxxxxxxxxxx.dkr.ecr.eu-west-1.amazonaws.com/tools/gh-terraform-runner:v0.1.73
      labels:
      - gh-terraform-secure
      organization: jumo
      resources:
        requests:
          cpu: "1"
          memory: 512Mi
      serviceAccountName: gh-terraform-secure-runner
      tolerations:
      - effect: NoSchedule
        key: runner-type
        operator: Equal
        value: gh-terraform-secure
To Reproduce
Go to: https://hub.docker.com/r/summerwind/actions-runner-dind-rootless/tags

Latest tag is v2.316.0-ubuntu-20.04-49490c4

Go to: https://hub.docker.com/r/summerwind/actions-runner-dind/tags

Latest tag is v2.317.0-ubuntu-20.04-8947327
Describe the bug

Latest image build (with runner version 2.317.0) for actions-runner-dind-rootless failed (for both ubuntu-20.04 and ubuntu-22.04): https://github.com/actions-runner-controller/releases/actions/runs/9415130587/job/25935482037

Describe the expected behavior

I would expect an image would be available with runner version 2.317.0, same as for the other images built from this repository.

Whole Controller Logs
N/A
Whole Runner Pod Logs
√ Settings Saved.

2024-06-10 13:29:13.952  DEBUG --- Runner successfully configured.
{
  "agentId": 1044721,
  "agentName": "gh-terraform-hsr79-5gf28",
  "poolId": 1,
  "poolName": "Default",
  "disableUpdate": true,
  "ephemeral": true,
  "serverUrl": "https://pipelinesghubeus21.actions.githubusercontent.com/xxxxxxx/",
  "gitHubUrl": "https://github.com/jumo",
  "workFolder": "/runner/_work"
2024-06-10 13:29:13.955  NOTICE --- Docker wait check skipped. Either Docker is disabled or the wait is disabled, continuing with entrypoint
2024-06-10 13:29:13.956  NOTICE --- WARNING LATEST TAG HAS BEEN DEPRECATED. SEE GITHUB ISSUE FOR DETAILS:
2024-06-10 13:29:13.957  NOTICE --- https://github.com/actions/actions-runner-controller/issues/2056
}
√ Connected to GitHub

Current runner version: '2.316.0'
2024-06-10 13:29:16Z: Listening for Jobs
An error occured: Runner version v2.316.0 is deprecated and cannot receive messages.
Runner listener exit with terminated error, stop the service, no retry needed.
Exiting runner...
2024-06-10 13:29:16.469  NOTICE --- Runner init exited. Exiting this process with code 0 so that the container and the pod is GC'ed Kubernetes soon.
Additional Context
Lenguaje dominante
Go
Estrellas
6.7k
Forks
1.5k
Merge medio
1 h 34 min
PR fusionados (30 d)
5

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de actions/actions-runner-controller

Todos los issues de actions/actions-runner-controller

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.