Closed bayandin closed 1 month ago
Since we're doing docker login
in CI (and locally), maybe it's better to rely on the credentials stored in the docker cli config (~/.docker/config.json
)? As shown in the example in this comment.
Since we're doing
docker login
in CI (and locally), maybe it's better to rely on the credentials stored in the docker cli config (~/.docker/config.json
)? As shown in the example in this comment.
Nice! Added it to the Issue description as an idea for implementation
Assigning to @bayandin, as there is a draft PR from him.
Just hit this here, I think: https://github.com/neondatabase/autoscaling/actions/runs/9574058662/job/26396646325?pr=974
Unassigning @bayandin ; the PR has been closed for now.
Problem description / Motivation
vm-builder
might fail if we send too many requests to docker hub from our hosts:Ref https://github.com/neondatabase/neon/actions/runs/7960954540/job/21732689596
To avoid this, we, usually, use authorised access to docker hub, but it seems docker go SDK doesn't pick up auth from DOCKER_CONFIG directory automatically (https://github.com/moby/moby/issues/39377#issuecomment-503589708), so we need to make it possible to pass docker user/password as additional
vm-builder
parameters.Feature idea(s) / DoD
Implementation ideas