Closed jpkrohling closed 1 year ago
Looks like long pull times from docker hub. @jpkrohling do you happen to know if the docker login secrets are available to the build-and-test integration-tests* job: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/ca4bfe1c4a9305a291397fc0ae2810ef5c7da039/.github/workflows/build-and-test.yml#L406? I think adding caching is one way to help with this. We could also run a local registry and use the actions/cache action: https://github.com/dtinth/github-actions-docker-layer-caching-poc/blob/210fdfb3f3b536a3e5dbea37da5f1bb8b285f84b/.github/workflows/dockerimage.yml#L33
do you happen to know if the docker login secrets are available to the build-and-test integration-tests* job:
There are no such secrets defined for this project. Should I just set my own credentials for now?
Decided to test out using ghcr.io instead to see if it makes a difference. see https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/6110. Not sure if this will make a difference or not, since pulling from dockerhub usually happens within seconds, maybe something else is going on there..
I'll set my own credentials for now, and let's see how it compares. If it still causes a problem, we should definitely go for your proposal.
Both DOCKER_USERNAME and DOCKER_PASSWORD are now available as a secret.
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers
. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Pinging code owners: @rmfitzpatrick @jamesmoessis. See Adding Labels via Comments if you do not have permissions to add labels yourself.
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers
. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers
. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
@codeboten do you still want to change the docker registry? I notice that the PR was closed as inactive. I recommend we close this bug as we don't have any reports for the last year.
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers
. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
This issue has been closed as inactive because it has been stale for 120 days with no activity.
Seen here: https://github.com/open-telemetry/opentelemetry-collector-contrib/runs/4038604844?check_suite_focus=true