Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
None
Description
We have Ubuntu-based CUDA-enabled builds using Docker images that evidently have not been exercised in a long time:
$ archery docker run ubuntu-cuda-cpp Pulling ubuntu-cuda-cpp ... done WARNING: Some service image(s) must be built from source by running: docker-compose build ubuntu-cuda-cpp Building ubuntu-cuda-cpp [+] Building 0.9s (4/4) FINISHED => [internal] load build definition from ubuntu-20.04-cpp.dockerfile 0.0s => => transferring dockerfile: 5.39kB 0.0s => [internal] load .dockerignore 0.0s => => transferring context: 35B 0.0s => ERROR [internal] load metadata for docker.io/nvidia/cuda:9.1-devel-ubuntu20.04 0.9s => [auth] nvidia/cuda:pull token for registry-1.docker.io 0.0s ------ > [internal] load metadata for docker.io/nvidia/cuda:9.1-devel-ubuntu20.04: ------ failed to solve with frontend dockerfile.v0: failed to create LLB definition: docker.io/nvidia/cuda:9.1-devel-ubuntu20.04: not found ERROR: Service 'ubuntu-cuda-cpp' failed to build : Build failed Error: `docker-compose --file /home/antoine/arrow/dev/docker-compose.yml build --build-arg BUILDKIT_INLINE_CACHE=1 ubuntu-cuda-cpp` exited with a non-zero exit code 1, see the process log above.
Attachments
Issue Links
- is depended upon by
-
ARROW-16464 [C++][CI][GPU] Add CUDA CI
- Resolved
-
ARROW-17435 [CI][Python] Install Numba on CUDA images
- Resolved
- links to