Note that the Python versions are now in sync (but weirdly the dask versions are now out of sync).
Problems
Conda pack doesn't always seem to do the right thing. In the example above the workers end up with dask/distributed 2022.7.0 got installed with pip when I installed dask-agent, not 2022.10.2 which I installed with conda (and seems to be picked up by default).
The scheduler isn't included so version mismatches could be problematic there
Local/editable installs seem to be ignored/broken
The scheduler sends the environment to agents sequentially.
reprovision_nodes
callconda-pack
Quick example using Dask Kubernetes
Note that the Python versions between the client and workers are mismatched.
Note that the Python versions are now in sync (but weirdly the
dask
versions are now out of sync).Problems
dask-agent
, not 2022.10.2 which I installed with conda (and seems to be picked up by default).