fix the pytorch var in the dockerfile #39
winglianAnnotations
5 errors and 6 warnings
|
build-base (121, 12.1.0, 3.10, 2.1.0, whl/nightly, 7.0 7.5 8.0 8.6 9.0+PTX)
buildx failed with: ERROR: failed to solve: process "/bin/sh -c python3 -m pip install --upgrade pip && pip3 install packaging && python3 -m pip install --no-cache-dir -U torch==${PYTORCH_VERSION} torchvision torchaudio --extra-index-url https://download.pytorch.org/$PYTORCH_INDEX/cu$CUDA" did not complete successfully: exit code: 1
|
|
build-base (118, 11.8.0, 3.9, 2.0.1, whl, 7.0 7.5 8.0 8.6+PTX)
The self-hosted runner: ip-172-30-2-176 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
build-base (118, 11.8.0, 3.9, 2.0.1, whl, gptq, 7.0 7.5 8.0 8.6+PTX)
The self-hosted runner: ip-172-30-2-7 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
build-base (117, 11.7.1, 3.9, 1.13.1, whl, 7.0 7.5 8.0 8.6+PTX)
The self-hosted runner: ip-172-30-2-117 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
build-base (118, 11.8.0, 3.10, 2.0.1, whl, 7.0 7.5 8.0 8.6+PTX)
The self-hosted runner: ip-172-30-2-167 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
build-base (121, 12.1.0, 3.10, 2.1.0, whl/nightly, 7.0 7.5 8.0 8.6 9.0+PTX)
The following actions uses node12 which is deprecated and will be forced to run on node16: docker/metadata-action@v3. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
build-base (121, 12.1.0, 3.10, 2.1.0, whl/nightly, 7.0 7.5 8.0 8.6 9.0+PTX)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
build-base (121, 12.1.0, 3.10, 2.1.0, whl/nightly, 7.0 7.5 8.0 8.6 9.0+PTX)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
build-base (121, 12.1.0, 3.10, 2.1.0, whl/nightly, 7.0 7.5 8.0 8.6 9.0+PTX)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
build-base (121, 12.1.0, 3.10, 2.1.0, whl/nightly, 7.0 7.5 8.0 8.6 9.0+PTX)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
build-base (121, 12.1.0, 3.10, 2.1.0, whl/nightly, 7.0 7.5 8.0 8.6 9.0+PTX)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|