-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dask-gateway image far behind mainline dask version. #405
Comments
Are you matching your worker environment to your singleuser pod, as documented at https://github.com/dask/helm-chart/tree/main/daskhub#matching-the-user-environment? That's usually the safest way to ensure you don't have mismatches between your singleuser and worker pods. |
Followed the docs your refered to. The scheduler pod seems to throw an exception at startup: Traceback (most recent call last):
File "/srv/conda/envs/notebook/bin/dask-scheduler", line 11, in <module>
sys.exit(go())
File "/srv/conda/envs/notebook/lib/python3.7/site-packages/distributed/cli/dask_scheduler.py", line 226, in go
main()
File "/srv/conda/envs/notebook/lib/python3.7/site-packages/click/core.py", line 829, in __call__
return self.main(*args, **kwargs)
File "/srv/conda/envs/notebook/lib/python3.7/site-packages/click/core.py", line 781, in main
with self.make_context(prog_name, args, **extra) as ctx:
File "/srv/conda/envs/notebook/lib/python3.7/site-packages/click/core.py", line 700, in make_context
self.parse_args(ctx, args)
File "/srv/conda/envs/notebook/lib/python3.7/site-packages/click/core.py", line 1048, in parse_args
value, args = param.handle_parse_result(ctx, opts, args)
File "/srv/conda/envs/notebook/lib/python3.7/site-packages/click/core.py", line 1630, in handle_parse_result
value = invoke_param_callback(self.callback, ctx, self, value)
File "/srv/conda/envs/notebook/lib/python3.7/site-packages/click/core.py", line 123, in invoke_param_callback
return callback(ctx, param, value)
File "/srv/conda/envs/notebook/lib/python3.7/site-packages/distributed/preloading.py", line 39, in validate_preload_argv
for name in ctx.params.get("preload")
File "/srv/conda/envs/notebook/lib/python3.7/site-packages/distributed/preloading.py", line 40, in <dictcomp>
if not is_webaddress(name)
File "/srv/conda/envs/notebook/lib/python3.7/site-packages/distributed/preloading.py", line 108, in _import_module
import_module(name)
File "/srv/conda/envs/notebook/lib/python3.7/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
File "<frozen importlib._bootstrap>", line 983, in _find_and_load
File "<frozen importlib._bootstrap>", line 965, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'dask_gateway.scheduler_preload'
Changing the option handler from # config.yaml
jupyterhub:
singleuser:
extraEnv:
DASK_GATEWAY__CLUSTER__OPTIONS__IMAGE: '{JUPYTER_IMAGE_SPEC}'
dask-gateway:
gateway:
extraConfig:
optionHandler: |
from dask_gateway_server.options import Options, Integer, Float, String
def option_handler(options):
if ":" not in options.image:
raise ValueError("When specifying an image you must also provide a tag")
return {
"image": options.image,
}
c.Backend.cluster_options = Options(
String("image", default="pangeo/base-notebook:latest", label="Image"),
handler=option_handler,
) However, things need not be this complicated. This also works: dask-gateway:
gateway:
backend:
image:
name: pangeo/base-notebook
tag: "latest" |
xref dask/dask-docker#144 It would be good to build an image as part of the Dask org which works with Dask gateway instead of using the one from the Pangeo community. |
I believe this was fixed in #413 |
The dockerfile was updated, but is there a new image? (I don't know if CI builds this dockerfile, or still pulls the latest from dockerhub) |
Ah, yes that's true. Seems like the last image was created about 9 months ago probably @jcrist did it manually. We can write a GitHub Action to build and push image to dockerhub on every merge to master? |
That seems reasonable; although that could be a lot of images, so maybe should be controlled by the commit message, or only for tags? @jacobtomlinson , you must have done this sort of thing. |
There are two images right? The Then there are the user environment containers that are configurable, and the default is to use the Pangeo image. For the We should also publish an image for the user environment, this is covered by dask/dask-docker#144. |
What happened:
dask-gateway docker image includes dask
2.30.0
, while the latest dask-version is2021.6.2
.What you expected to happen:
dask-gateway docker image should include dash version
2021.6.0
or greaterMinimal Complete Verifiable Example:
Simply create new daskhub-deployment based on
daskhub
helm-chart, then spawn a new cluster:Anything else we need to know?:
This issue causes helm-chart
daskhub
to to fail when spawning new clusters.Environment:
The text was updated successfully, but these errors were encountered: