Skip to content

chore(server,worker): optimize Dockerfile #2988

chore(server,worker): optimize Dockerfile

chore(server,worker): optimize Dockerfile #2988

Triggered via push October 18, 2024 11:58
Status Failure
Total duration 4m 12s
Artifacts

ci.yml

on: push
prepare
9s
prepare
ci-extension  /  ci-extension
ci-extension / ci-extension
ci-geo  /  ci
ci-geo / ci
ci-server  /  ci-server-lint
21s
ci-server / ci-server-lint
ci-server  /  ci-server-test
1m 7s
ci-server / ci-server-test
ci-tiles  /  ci
ci-tiles / ci
ci-worker  /  ci-worker-lint
2m 42s
ci-worker / ci-worker-lint
ci-worker  /  ci-worker-test
18s
ci-worker / ci-worker-test
ci-tools  /  ci-tools
ci-tools / ci-tools
deploy-extension-dev
0s
deploy-extension-dev
build-geo  /  Build and push Docker image
build-geo / Build and push Docker image
build-server  /  Build and push Docker image
22s
build-server / Build and push Docker image
build-tiles  /  Build and push Docker image
build-tiles / Build and push Docker image
build-worker  /  Build and push Docker image
53s
build-worker / Build and push Docker image
Matrix: ci-tools / ci-tools-build
Waiting for pending jobs
deploy-geo-dev
0s
deploy-geo-dev
deploy-server-dev
0s
deploy-server-dev
deploy-tiles-dev
0s
deploy-tiles-dev
deploy-worker-dev
0s
deploy-worker-dev
ci-tools  /  ci-tools-release
ci-tools / ci-tools-release
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 7 warnings
build-server / Build and push Docker image
buildx failed with: ERROR: failed to solve: golang:1.22-bullseye: failed to resolve source metadata for docker.io/library/golang:1.22-bullseye: failed to authorize: failed to fetch oauth token: unexpected status from POST request to https://auth.docker.io/token: 502 Bad Gateway
build-worker / Build and push Docker image
buildx failed with: ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref ca20b4bh6e1ka0jn5s916xw1e::fpk6uv3o397dy26swoa3135zu: "/go/bin/gcsfuse": not found
prepare
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, tj-actions/changed-files@v36. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ci-worker / ci-worker-test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ci-server / ci-server-lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, golangci/golangci-lint-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ci-server / ci-server-test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build-server / Build and push Docker image
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/setup-buildx-action@v2, dawidd6/action-download-artifact@v2, docker/build-push-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ci-worker / ci-worker-lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, golangci/golangci-lint-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build-worker / Build and push Docker image
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/setup-buildx-action@v2, docker/build-push-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/