Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

org.opencontainers.image.source label is incorrect

Abierto
  • ¿Algo no está bien?
#78 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
docker, dockerfile, github-actions
Área
ci-cd, devops

Línea de trabajo

Inspecciona la lógica de GitHub Action que genera la etiqueta org.opencontainers.image.source y compárala con el manejo existente de image.url. Reproduce el problema usando los valores proporcionados de organization, registry, image_name y repository; la tarea estará terminada cuando la etiqueta source identifique el repositorio real de GitHub o admita el override explícito propuesto.

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

Descripción

bug

Found a bug? Maybe our Slack Community can help.

Slack Community

Describe the Bug

org.opencontainers.image.source=https://github.com/${{ inputs.organization }}/${{ inputs.repository }} is an invalid label when the org/repo approach are not used so you have to put improper values to fix this label.

The image.url label would be accurate to the actual GH repo, if the values are the same.

Expected Behavior

Create a proper label for the image.source like it does for image.url.

Steps to Reproduce

Steps to reproduce the behavior:

  1. Run the GHA with input values unrelated to the current repo
  2. Observe the label is incorrect.

Example:

Inputs:

    organization: client
    registry: client.jfrog.io
    image_name: example-image
    repository: jfrog-non-prod

Creates a label like this:

--label org.opencontainers.image.source=https://github.com/client/jfrog-non-prod

If you don't provide a repository since it is included in the image name or if the GH repo is different from the docker image repo, the label will perpetually be wrong unless you set the repo input to a value solely for satisfying this label.

    organization: client
    registry: client.jfrog.io
    image_name: jfrog-non-prod/example-image
    repository: example-image

What if the GH repo is under a completely different name than the docker image name? Something where there is a client-sandbox GH org that is pushing to the client org so the label would also be wrong there as well.

Suggestion: update the logic for that label to match that of image.url and allow an override based on a new input.

Screenshots

This is internal client work so I cannot provide the screenshot and blurring private info would remove the usefulness.

Environment (please complete the following information):

Anything that will help us triage the bug will help. Here are some ideas:

  • OS: N/A
  • Version [e.g. 10.15]: N/A

Additional Context

This is active in the 1.17.2 version.

Lenguaje dominante
Dockerfile
Estrellas
14
Forks
15
Merge medio
8 h 45 min
PR fusionados (30 d)
1

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 cloudposse/github-action-docker-build-push

Todos los issues de cloudposse/github-action-docker-build-push

Issues similares

Más issues de DevOps

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.