-
Notifications
You must be signed in to change notification settings - Fork 3
hardcoded NFS IP's #2
Comments
Hi Sven, first of all thanks for showing interest in my repo. I am currently updating the Jupyterhub Dockerfile from To make things clear for you:
Of course this isn't the case. You first have to modify the config of your setup. In the To make thinks clear. The When launching the jupyterhub as a Docker Service from the Docker Host, the Docker Host creates Docker Volumes (with type nfs4) mapped to the I hope this could clear things up for you. I know that the documentation is not very helpful right know, but I will updated it as soon as I completed |
I thought I'd be able to just clone and
make run
as the docs say - but it looks like (I've only just begun to dig) the nfs container (andjupyterhub-network
) don't have the IP addresses you've put in.env
- and so the hub container can't start.Sadly, Docker Swarm's error reporting is about as unhelpful as possible - the only state info I can derive, is from
The text was updated successfully, but these errors were encountered: