Skip to content

Docker builds

Docker builds #55

Triggered via schedule February 20, 2024 00:09
Status Failure
Total duration 6m 43s
Artifacts

docker-build.yml

on: schedule
Matrix: build-cuda
Matrix: build-pl
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 5 warnings
build-NGC
buildx failed with: ERROR: failed to solve: failed to register layer: write /opt/conda/lib/python3.8/site-packages/torch/test/c10_Synchronized_test: no space left on device
build-cuda (3.9, 1.12, 11.7.1)
No SLACK_WEBHOOK_URL provided
build-cuda (3.9, 1.12, 11.7.1)
buildx failed with: ERROR: failed to solve: failed to push pytorchlightning/pytorch_lightning:base-cuda-py3.9-torch1.12-cuda11.7.1: failed to authorize: failed to fetch oauth token: unexpected status from GET request to https://auth.docker.io/token?scope=repository%3Apytorchlightning%2Fpytorch_lightning%3Apull%2Cpush&service=registry.docker.io: 401 Unauthorized
build-cuda (3.9, 1.13, 11.8.0)
No SLACK_WEBHOOK_URL provided
build-cuda (3.9, 1.13, 11.8.0)
buildx failed with: ERROR: failed to solve: failed to push pytorchlightning/pytorch_lightning:base-cuda-py3.9-torch1.13-cuda11.8.0: failed to authorize: failed to fetch oauth token: unexpected status from GET request to https://auth.docker.io/token?scope=repository%3Apytorchlightning%2Fpytorch_lightning%3Apull%2Cpush&service=registry.docker.io: 401 Unauthorized
build-cuda (3.10, 2.0, 11.8.0)
No SLACK_WEBHOOK_URL provided
build-cuda (3.10, 2.0, 11.8.0)
buildx failed with: ERROR: failed to solve: failed to push pytorchlightning/pytorch_lightning:base-cuda-py3.10-torch2.0-cuda11.8.0: failed to authorize: failed to fetch oauth token: unexpected status from GET request to https://auth.docker.io/token?scope=repository%3Apytorchlightning%2Fpytorch_lightning%3Apull%2Cpush&service=registry.docker.io: 401 Unauthorized
build-cuda (3.9, 1.13, 12.0.1)
buildx failed with: ERROR: failed to solve: failed to push pytorchlightning/pytorch_lightning:base-cuda-py3.9-torch1.13-cuda12.0.1: failed to authorize: failed to fetch oauth token: unexpected status from GET request to https://auth.docker.io/token?scope=repository%3Apytorchlightning%2Fpytorch_lightning%3Apull%2Cpush&service=registry.docker.io: 401 Unauthorized
build-cuda (3.9, 1.13, 12.0.1)
No SLACK_WEBHOOK_URL provided
build-cuda (3.10, 2.1, 12.1.0)
No SLACK_WEBHOOK_URL provided
build-cuda (3.10, 2.1, 12.1.0)
buildx failed with: ERROR: failed to solve: failed to push pytorchlightning/pytorch_lightning:base-cuda-py3.10-torch2.1-cuda12.1.0: failed to authorize: failed to fetch oauth token: unexpected status from GET request to https://auth.docker.io/token?scope=repository%3Apytorchlightning%2Fpytorch_lightning%3Apull%2Cpush&service=registry.docker.io: 401 Unauthorized
build-cuda (3.9, 1.12, 11.7.1)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: ravsamhq/notify-slack-action@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build-cuda (3.9, 1.13, 11.8.0)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: ravsamhq/notify-slack-action@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build-cuda (3.10, 2.0, 11.8.0)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: ravsamhq/notify-slack-action@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build-cuda (3.9, 1.13, 12.0.1)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: ravsamhq/notify-slack-action@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build-cuda (3.10, 2.1, 12.1.0)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: ravsamhq/notify-slack-action@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.