Skip to content

bug: Failed to deploy project: Error building image #1636

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
NicWagenaar opened this issue Jan 24, 2025 · 2 comments
Closed

bug: Failed to deploy project: Error building image #1636

NicWagenaar opened this issue Jan 24, 2025 · 2 comments

Comments

@NicWagenaar
Copy link

NicWagenaar commented Jan 24, 2025

Provide environment information

System:
OS: macOS 14.4.1
CPU: (8) arm64 Apple M1
Memory: 61.09 MB / 8.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.11.1 - ~/.nvm/versions/node/v20.11.1/bin/node
npm: 10.2.4 - ~/.nvm/versions/node/v20.11.1/bin/npm

Describe the bug

I'm trying to deploy to our staging environment. The project builds successfully, but fails at the deploy step. See below for the full docker build log. It seems like it's some problem with the registry.

I'm using Trigger version 3.3.11 as follows:
npx [email protected] deploy --env staging

#1 [depot] launching amd64 machine
#1 DONE 7.9s
#2 [depot] connecting to amd64 machine
#2 DONE 0.7s
#3 [internal] fetching git attributes
#3 DONE 1.6s
#4 [internal] load build definition from Containerfile
#4 transferring dockerfile: 33B 0.1s
#4 transferring dockerfile: 2.94kB 0.4s done
#4 DONE 0.4s
#5 resolve image config for docker-image://docker.io/docker/dockerfile:1
#5 DONE 0.8s
#6 docker-image://docker.io/docker/dockerfile:1@sha256:93bfd3b68c109427185cd78b4779fc82b484b0b7618e36d0f104d4d801e66d25
#6 resolve docker.io/docker/dockerfile:1@sha256:93bfd3b68c109427185cd78b4779fc82b484b0b7618e36d0f104d4d801e66d25 0.0s done
#6 CACHED
#4 [internal] load build definition from Containerfile
#4 transferring dockerfile: 2.94kB 0.4s done
#4 DONE 0.4s
#7 [internal] load build definition from Containerfile
#7 Deduplicating step ID [internal] load build definition from Containerfile, another build is calculating it done
#7 DONE 0.0s
#8 [internal] load metadata for docker.io/library/node:21-bookworm-slim@sha256:99afef5df7400a8d118e0504576d32ca700de5034c4f9271d2ff7c91cc12d170
#8 DONE 0.4s
#9 [internal] load .dockerignore
#9 transferring context: 0.1s
#9 transferring context: 2B 0.2s done
#9 DONE 0.3s
#10 [internal] load build context
#10 DONE 0.0s
#11 [base 1/2] FROM docker.io/library/node:21-bookworm-slim@sha256:99afef5df7400a8d118e0504576d32ca700de5034c4f9271d2ff7c91cc12d170
#11 resolve docker.io/library/node:21-bookworm-slim@sha256:99afef5df7400a8d118e0504576d32ca700de5034c4f9271d2ff7c91cc12d170
#11 resolve docker.io/library/node:21-bookworm-slim@sha256:99afef5df7400a8d118e0504576d32ca700de5034c4f9271d2ff7c91cc12d170 done
#11 DONE 0.0s
#10 [internal] load build context
#10 transferring context: 981.23kB 4.1s
#10 transferring context: 8.06MB 9.2s
#10 transferring context: 15.40MB 11.0s done
#10 DONE 11.1s
#12 [build 2/6] WORKDIR /app
#12 CACHED
#13 [build 3/6] COPY --chown=node:node package.json ./
#13 CACHED
#14 [base 2/2] RUN apt-get update && apt-get --fix-broken install -y && apt-get install -y --no-install-recommends busybox ca-certificates dumb-init git openssl && apt-get clean && rm -rf /var/lib/apt/lists/*
#14 CACHED
#15 [build 1/6] RUN apt-get update && apt-get install -y --no-install-recommends     python3 make g++ &&     apt-get clean && rm -rf /var/lib/apt/lists/*
#15 CACHED
#16 [build 4/6] RUN npm i --no-audit --no-fund --no-save --no-package-lock
#16 CACHED
#17 [build 5/6] COPY --chown=node:node . .
#17 DONE 0.2s
#18 [build 6/6] COPY --chown=node:node . .
#18 DONE 0.1s
#19 [indexer 1/2] WORKDIR /app
#19 DONE 0.1s
#20 [indexer 2/2] RUN node /app/.npm/_npx/d002ce1b0683ad5c/node_modules/trigger.dev/dist/esm/entryPoints/deploy-index-controller.mjs
#20 ...
#21 [final 1/3] WORKDIR /app
#21 CACHED
#20 [indexer 2/2] RUN node /app/.npm/_npx/d002ce1b0683ad5c/node_modules/trigger.dev/dist/esm/entryPoints/deploy-index-controller.mjs
#20 1.480 Writing index.json /app
#20 ...
#22 [final 2/3] COPY --from=build --chown=node:node /app ./
#22 DONE 0.2s
#20 [indexer 2/2] RUN node /app/.npm/_npx/d002ce1b0683ad5c/node_modules/trigger.dev/dist/esm/entryPoints/deploy-index-controller.mjs
#20 DONE 3.3s
#23 [final 3/3] COPY --from=indexer --chown=node:node /app/index.json ./
#23 DONE 0.3s
#24 exporting to image
#24 exporting layers
#24 ...
#25 [auth] sharing credentials for registry.trigger.dev
#25 DONE 0.0s
#24 exporting to image
#24 exporting layers 0.3s done
#24 exporting manifest sha256:aa37470f5a82ce08d210f5ae7f87c23b60432a5bc9bc92d88023297c79062786 0.0s done
#24 exporting config sha256:fdc9b1a0f871b4d3050c96bc1ac482d053b2e3255b79938240b0ac92b24b56fd 0.0s done
#24 pushing layers for registry.trigger.dev/trigger-failover/proj_sdyhznurvxknuqmcvprr:20250124.5.stg@sha256:aa37470f5a82ce08d210f5ae7f87c23b60432a5bc9bc92d88023297c79062786
#24 pushing layer sha256:bbe36f8dd7f0e537aa34fbe435d4342b620e40aeecafe91c4d9ffa7172d32912
#24 pushing layer sha256:2e82ac84e1512655a99357cfdf7916a8f67a7d47c7c2314bf2172861c00abd72
#24 pushing layer sha256:09f376ebb190216b0459f470e71bec7b5dfa611d66bf008492b40dcc5f1d8eae
#24 pushing layer sha256:a2837574e7c9422a3cc93cef8bebbe050c0aee64ff43a97bfb4b4fb29fca439b
#24 pushing layer sha256:9f1c458e7f2d5d570229bfeedfc0b1701e008a3a2920e95d0cb6b676e62b987b
#24 pushing layer sha256:30e51537f486caf3878e63f3dc6038db0a6abf5698ab86bd2080be44287f55e3
#24 pushing layer sha256:5885e07b26d098e6585feafda6cddc62fd51bf7ae76b92b5441d66640f797fb5
#24 pushing layer sha256:fdc9b1a0f871b4d3050c96bc1ac482d053b2e3255b79938240b0ac92b24b56fd
#24 pushing layer sha256:3f821551f5d31460f6d574bae43b6591f494acb1e4c995d385d81555d9efe7bc
#24 pushing layer sha256:44f5fe9df22b4c549ef3e662bd64e1e6edb8d3738224047ce56d83ab2f498943
#24 pushing layer sha256:3f821551f5d31460f6d574bae43b6591f494acb1e4c995d385d81555d9efe7bc 1.3s done
#24 pushing layer sha256:44f5fe9df22b4c549ef3e662bd64e1e6edb8d3738224047ce56d83ab2f498943 1.3s done
#24 pushing layer sha256:5885e07b26d098e6585feafda6cddc62fd51bf7ae76b92b5441d66640f797fb5 2.9s done
#24 pushing layer sha256:09f376ebb190216b0459f470e71bec7b5dfa611d66bf008492b40dcc5f1d8eae 3.1s done
#24 pushing layer sha256:30e51537f486caf3878e63f3dc6038db0a6abf5698ab86bd2080be44287f55e3 4.7s done
#24 pushing layer sha256:2e82ac84e1512655a99357cfdf7916a8f67a7d47c7c2314bf2172861c00abd72 5.7s done
#24 pushing layer sha256:9f1c458e7f2d5d570229bfeedfc0b1701e008a3a2920e95d0cb6b676e62b987b 5.7s done
#24 8.149 error: failed commit on ref "layer-sha256:a2837574e7c9422a3cc93cef8bebbe050c0aee64ff43a97bfb4b4fb29fca439b": unexpected status from PUT request to https://registry.trigger.dev/v2/trigger-failover/proj_sdyhznurvxknuqmcvprr/blobs/uploads/c5186532-9a3b-48e9-b913-a2fb9503cf5f?_state=bz4JDEz48tK5pfS3EOalA6RQtfHiwWQZyyXueL5d0Ht7Ik5hbWUiOiJ0cmlnZ2VyLWZhaWxvdmVyL3Byb2pfc2R5aHpudXJ2eGtudXFtY3ZwcnIiLCJVVUlEIjoiYzUxODY1MzItOWEzYi00OGU5LWI5MTMtYTJmYjk1MDNjZjVmIiwiT2Zmc2V0IjowLCJTdGFydGVkQXQiOiIyMDI1LTAxLTI0VDEyOjI3OjM1LjExNjAzODAyM1oifQ%3D%3D&digest=sha256%3Aa2837574e7c9422a3cc93cef8bebbe050c0aee64ff43a97bfb4b4fb29fca439b: 520 unknown
#24 8.149 retrying in 1s
#24 14.69 error: failed commit on ref "layer-sha256:a2837574e7c9422a3cc93cef8bebbe050c0aee64ff43a97bfb4b4fb29fca439b": unexpected status from PUT request to https://registry.trigger.dev/v2/trigger-failover/proj_sdyhznurvxknuqmcvprr/blobs/uploads/e1db8e91-2364-42c1-81ff-f8bb62631241?_state=Af_b63KAJe8K5gL_8efZAsSjfUR1vugyXtTx0LLSQLp7Ik5hbWUiOiJ0cmlnZ2VyLWZhaWxvdmVyL3Byb2pfc2R5aHpudXJ2eGtudXFtY3ZwcnIiLCJVVUlEIjoiZTFkYjhlOTEtMjM2NC00MmMxLTgxZmYtZjhiYjYyNjMxMjQxIiwiT2Zmc2V0IjowLCJTdGFydGVkQXQiOiIyMDI1LTAxLTI0VDEyOjI3OjQxLjY1NTA1NzM2MloifQ%3D%3D&digest=sha256%3Aa2837574e7c9422a3cc93cef8bebbe050c0aee64ff43a97bfb4b4fb29fca439b: 520 unknown
#24 14.69 retrying in 2s
#24 pushing layer sha256:bbe36f8dd7f0e537aa34fbe435d4342b620e40aeecafe91c4d9ffa7172d32912 14.9s done
#24 pushing layer sha256:fdc9b1a0f871b4d3050c96bc1ac482d053b2e3255b79938240b0ac92b24b56fd 15.5s done
#24 25.38 error: failed commit on ref "layer-sha256:a2837574e7c9422a3cc93cef8bebbe050c0aee64ff43a97bfb4b4fb29fca439b": unexpected status from PUT request to https://registry.trigger.dev/v2/trigger-failover/proj_sdyhznurvxknuqmcvprr/blobs/uploads/b3dbcb4f-d036-40c6-be12-d88c9030d66c?_state=-cHh7E9QdAwlz-_No5PpQ_vQY468HQHeBbguTXUGB-Z7Ik5hbWUiOiJ0cmlnZ2VyLWZhaWxvdmVyL3Byb2pfc2R5aHpudXJ2eGtudXFtY3ZwcnIiLCJVVUlEIjoiYjNkYmNiNGYtZDAzNi00MGM2LWJlMTItZDg4YzkwMzBkNjZjIiwiT2Zmc2V0IjowLCJTdGFydGVkQXQiOiIyMDI1LTAxLTI0VDEyOjI3OjUyLjMzMTMxMDE0MVoifQ%3D%3D&digest=sha256%3Aa2837574e7c9422a3cc93cef8bebbe050c0aee64ff43a97bfb4b4fb29fca439b: 520 unknown
#24 25.38 retrying in 4s
#24 pushing layers for registry.trigger.dev/trigger-failover/proj_sdyhznurvxknuqmcvprr:20250124.5.stg@sha256:aa37470f5a82ce08d210f5ae7f87c23b60432a5bc9bc92d88023297c79062786 37.8s done
#24 pushing layer sha256:a2837574e7c9422a3cc93cef8bebbe050c0aee64ff43a97bfb4b4fb29fca439b 37.8s done
#24 38.16 error: failed commit on ref "layer-sha256:a2837574e7c9422a3cc93cef8bebbe050c0aee64ff43a97bfb4b4fb29fca439b": unexpected status from PUT request to https://registry.trigger.dev/v2/trigger-failover/proj_sdyhznurvxknuqmcvprr/blobs/uploads/769030ce-97bc-4e6b-80f0-d47ce4ca5c0a?_state=g5d1Frv_m9iUiZKr91aaQ2aDLrdn8VYAg--JQZpNAOV7Ik5hbWUiOiJ0cmlnZ2VyLWZhaWxvdmVyL3Byb2pfc2R5aHpudXJ2eGtudXFtY3ZwcnIiLCJVVUlEIjoiNzY5MDMwY2UtOTdiYy00ZTZiLTgwZjAtZDQ3Y2U0Y2E1YzBhIiwiT2Zmc2V0IjowLCJTdGFydGVkQXQiOiIyMDI1LTAxLTI0VDEyOjI4OjA1LjEzNjIwNDg2MloifQ%3D%3D&digest=sha256%3Aa2837574e7c9422a3cc93cef8bebbe050c0aee64ff43a97bfb4b4fb29fca439b: 520 unknown
#24 ERROR: failed to push registry.trigger.dev/trigger-failover/proj_sdyhznurvxknuqmcvprr:20250124.5.stg: failed commit on ref "layer-sha256:a2837574e7c9422a3cc93cef8bebbe050c0aee64ff43a97bfb4b4fb29fca439b": unexpected status from PUT request to https://registry.trigger.dev/v2/trigger-failover/proj_sdyhznurvxknuqmcvprr/blobs/uploads/769030ce-97bc-4e6b-80f0-d47ce4ca5c0a?_state=g5d1Frv_m9iUiZKr91aaQ2aDLrdn8VYAg--JQZpNAOV7Ik5hbWUiOiJ0cmlnZ2VyLWZhaWxvdmVyL3Byb2pfc2R5aHpudXJ2eGtudXFtY3ZwcnIiLCJVVUlEIjoiNzY5MDMwY2UtOTdiYy00ZTZiLTgwZjAtZDQ3Y2U0Y2E1YzBhIiwiT2Zmc2V0IjowLCJTdGFydGVkQXQiOiIyMDI1LTAxLTI0VDEyOjI4OjA1LjEzNjIwNDg2MloifQ%3D%3D&digest=sha256%3Aa2837574e7c9422a3cc93cef8bebbe050c0aee64ff43a97bfb4b4fb29fca439b: 520 unknown
------
> exporting to image:
#24 8.149 error: failed commit on ref "layer-sha256:a2837574e7c9422a3cc93cef8bebbe050c0aee64ff43a97bfb4b4fb29fca439b": unexpected status from PUT request to https://registry.trigger.dev/v2/trigger-failover/proj_sdyhznurvxknuqmcvprr/blobs/uploads/c5186532-9a3b-48e9-b913-a2fb9503cf5f?_state=bz4JDEz48tK5pfS3EOalA6RQtfHiwWQZyyXueL5d0Ht7Ik5hbWUiOiJ0cmlnZ2VyLWZhaWxvdmVyL3Byb2pfc2R5aHpudXJ2eGtudXFtY3ZwcnIiLCJVVUlEIjoiYzUxODY1MzItOWEzYi00OGU5LWI5MTMtYTJmYjk1MDNjZjVmIiwiT2Zmc2V0IjowLCJTdGFydGVkQXQiOiIyMDI1LTAxLTI0VDEyOjI3OjM1LjExNjAzODAyM1oifQ%3D%3D&digest=sha256%3Aa2837574e7c9422a3cc93cef8bebbe050c0aee64ff43a97bfb4b4fb29fca439b: 520 unknown
#24 8.149 retrying in 1s
#24 14.69 error: failed commit on ref "layer-sha256:a2837574e7c9422a3cc93cef8bebbe050c0aee64ff43a97bfb4b4fb29fca439b": unexpected status from PUT request to https://registry.trigger.dev/v2/trigger-failover/proj_sdyhznurvxknuqmcvprr/blobs/uploads/e1db8e91-2364-42c1-81ff-f8bb62631241?_state=Af_b63KAJe8K5gL_8efZAsSjfUR1vugyXtTx0LLSQLp7Ik5hbWUiOiJ0cmlnZ2VyLWZhaWxvdmVyL3Byb2pfc2R5aHpudXJ2eGtudXFtY3ZwcnIiLCJVVUlEIjoiZTFkYjhlOTEtMjM2NC00MmMxLTgxZmYtZjhiYjYyNjMxMjQxIiwiT2Zmc2V0IjowLCJTdGFydGVkQXQiOiIyMDI1LTAxLTI0VDEyOjI3OjQxLjY1NTA1NzM2MloifQ%3D%3D&digest=sha256%3Aa2837574e7c9422a3cc93cef8bebbe050c0aee64ff43a97bfb4b4fb29fca439b: 520 unknown
#24 14.69 retrying in 2s
#24 25.38 error: failed commit on ref "layer-sha256:a2837574e7c9422a3cc93cef8bebbe050c0aee64ff43a97bfb4b4fb29fca439b": unexpected status from PUT request to https://registry.trigger.dev/v2/trigger-failover/proj_sdyhznurvxknuqmcvprr/blobs/uploads/b3dbcb4f-d036-40c6-be12-d88c9030d66c?_state=-cHh7E9QdAwlz-_No5PpQ_vQY468HQHeBbguTXUGB-Z7Ik5hbWUiOiJ0cmlnZ2VyLWZhaWxvdmVyL3Byb2pfc2R5aHpudXJ2eGtudXFtY3ZwcnIiLCJVVUlEIjoiYjNkYmNiNGYtZDAzNi00MGM2LWJlMTItZDg4YzkwMzBkNjZjIiwiT2Zmc2V0IjowLCJTdGFydGVkQXQiOiIyMDI1LTAxLTI0VDEyOjI3OjUyLjMzMTMxMDE0MVoifQ%3D%3D&digest=sha256%3Aa2837574e7c9422a3cc93cef8bebbe050c0aee64ff43a97bfb4b4fb29fca439b: 520 unknown
#24 25.38 retrying in 4s
#24 38.16 error: failed commit on ref "layer-sha256:a2837574e7c9422a3cc93cef8bebbe050c0aee64ff43a97bfb4b4fb29fca439b": unexpected status from PUT request to https://registry.trigger.dev/v2/trigger-failover/proj_sdyhznurvxknuqmcvprr/blobs/uploads/769030ce-97bc-4e6b-80f0-d47ce4ca5c0a?_state=g5d1Frv_m9iUiZKr91aaQ2aDLrdn8VYAg--JQZpNAOV7Ik5hbWUiOiJ0cmlnZ2VyLWZhaWxvdmVyL3Byb2pfc2R5aHpudXJ2eGtudXFtY3ZwcnIiLCJVVUlEIjoiNzY5MDMwY2UtOTdiYy00ZTZiLTgwZjAtZDQ3Y2U0Y2E1YzBhIiwiT2Zmc2V0IjowLCJTdGFydGVkQXQiOiIyMDI1LTAxLTI0VDEyOjI4OjA1LjEzNjIwNDg2MloifQ%3D%3D&digest=sha256%3Aa2837574e7c9422a3cc93cef8bebbe050c0aee64ff43a97bfb4b4fb29fca439b: 520 unknown
------
Error: failed to solve: failed to push registry.trigger.dev/trigger-failover/proj_sdyhznurvxknuqmcvprr:20250124.5.stg: failed commit on ref "layer-sha256:a2837574e7c9422a3cc93cef8bebbe050c0aee64ff43a97bfb4b4fb29fca439b": unexpected status from PUT request to https://registry.trigger.dev/v2/trigger-failover/proj_sdyhznurvxknuqmcvprr/blobs/uploads/769030ce-97bc-4e6b-80f0-d47ce4ca5c0a?_state=g5d1Frv_m9iUiZKr91aaQ2aDLrdn8VYAg--JQZpNAOV7Ik5hbWUiOiJ0cmlnZ2VyLWZhaWxvdmVyL3Byb2pfc2R5aHpudXJ2eGtudXFtY3ZwcnIiLCJVVUlEIjoiNzY5MDMwY2UtOTdiYy00ZTZiLTgwZjAtZDQ3Y2U0Y2E1YzBhIiwiT2Zmc2V0IjowLCJTdGFydGVkQXQiOiIyMDI1LTAxLTI0VDEyOjI4OjA1LjEzNjIwNDg2MloifQ%3D%3D&digest=sha256%3Aa2837574e7c9422a3cc93cef8bebbe050c0aee64ff43a97bfb4b4fb29fca439b: 520 unknown

Reproduction repo

N/A, this is happening in a private repo

To reproduce

Deploy any Trigger project using the following command:
npx [email protected] deploy --env staging

Additional information

This only affects deployment. Running the dev environment using npx [email protected] dev works without issue.

@venarius
Copy link

Yes, their registry seems to be currently down according to https://status.trigger.dev/

@matt-aitken
Copy link
Member

I'm closing this because this is not a bug with the code, it's an issue with one of our the services we use in the cloud product.

You can see the latest status here: https://status.trigger.dev/incident/500864?mp=true

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants