Closed jacobtomlinson closed 1 year ago
For reasons yet to be determined, Ubuntu 22 images are causing that error. We figured this out recently and have a "known issue" explanation going in docs very soon.
reasons yet to be determined
To be explicit, most likely seccomp
, good chance it's clone3
, I need to try change and verify everything works.
Thanks @ntabris, I can confirm that using our 20.04
based image works as expected.
In [1]: import coiled
...:
...: coiled.create_software_environment(
...: name="rapids-stable-23-04-docker",
...: account="dask",
...: container="nvcr.io/nvidia/rapidsai/rapidsai-core:23.04-cuda11.8-runtime-ubuntu20.04-py3.10",
...: )
Should be good to update your docs with the new versions though. I'll make a note in our docs that RAPIDS makes Ubuntu 22.04
the default base, but 20.04
is still available and required for Coiled for the time being.
@scharlottej13 docs update please when you get a minute
fyi @jacobtomlinson we'll deploy the fix so Ubuntu 22 works in the next day or two. I can make an issue or PR on rapidsai/deployment when this is out.
RAPIDS 23.04 is out.
I've just tried to spin up a Coiled cluster via both the docker and conda/mamba methods.
Conda
Docker
Both environments were created but when using them in a cluster only the conda method works but the Docker-based approach is failing and I see the following in the logs.
Could someone take a look at this?
Sidenote: The conda method is soooooo much faster, awesome stuff. Maybe it's worth switching the default example at the top of the GPU page to use that instead.