#Dagger starts to fail to push images after several `.publish()`

1 messages · Page 1 of 1 (latest)

noble ravine
#

I'm getting errors like the following, inconsistently

14:09:33  5 components failed to build
14:09:33  exit status 1
14:09:33  1312:   export layers DONE [3.1s]
14:09:33  1313:   remotes.docker.resolver.HTTPRequest
14:09:33  1314:   HTTP HEAD
14:09:33  1314:   HTTP HEAD ERROR [0.1s]
14:09:33  1313:   remotes.docker.resolver.HTTPRequest ERROR [0.1s]
14:09:33  1315:   remotes.docker.resolver.HTTPRequest
14:09:33  1316:   HTTP HEAD
14:09:33  1316:   HTTP HEAD ERROR [0.0s]
14:09:33  1315:   remotes.docker.resolver.HTTPRequest ERROR [0.0s]
14:09:33  1317:   remotes.docker.resolver.HTTPRequest
14:09:33  1318:   HTTP HEAD
14:09:33  1318:   HTTP HEAD ERROR [0.1s]
14:09:33  1317:   remotes.docker.resolver.HTTPRequest ERROR [0.1s]
14:09:33  1319:   remotes.docker.resolver.HTTPRequest
14:09:33  <img_name>: while uploading image to registry (us.gcr.io/<IMG_URI>) on host: input: container.from.withExec.withFile.withFile.withEntrypoint.publish resolve: failed to export: failed to push us.gcr.io/<IMG_URI>: failed to authorize: failed to fetch oauth token: unexpected status from POST request to https://us.gcr.io/v2/token: 404 Not Found
14:09:33  <img_name>: input: container.from.withExec.withFile.withMountedDirectory.withExec.withWorkdir.withMountedDirectory.directory.dockerBuild resolve: us.gcr.io/<org>/external/openresty/openresty:1.15.8.2-1-alpine: failed to resolve source metadata for us.gcr.io/<org>/external/openresty/openresty:1.15.8.2-1-alpine: unexpected status from HEAD request to https://us.gcr.io/v2/<org>/external/openresty/openresty/manifests/1.15.8.2-1-alpine: 401 Unauthorized

We have 20+ builds->push in a single dagger run and for some runs, it starts failing and then keeps failing for the remainder.

v0.14.0