Configuration Warnings: `hub_ip` and `hub_port` not recognized by DockerSpawner

[berceanu]

Description

I'm encountering configuration warnings when trying to set up communication between spawned containers and the JupyterHub. While my setup is functional, I'm receiving warnings that suggest the configuration options I'm using may be outdated or incorrect.

Error/Warnings

[W JupyterHub configurable:214] Config option `hub_ip` not recognized by `DockerSpawner`. Did you mean one of: `host_ip, hub_ip_connect`?
[W JupyterHub configurable:214] Config option `hub_port` not recognized by `DockerSpawner`. Did you mean one of: `hub_ip_connect, port`?

Environment

• Ubuntu 24.04 server
• JupyterHub running in a Python virtual environment
• DockerSpawner version: 5.2.1
• JupyterHub version: 14.0.0

Current Configuration

The relevant parts of my jupyterhub_config.py:

# How spawned containers connect back to the Hub
c.DockerSpawner.hub_ip = '172.18.0.1'  # IP of the hub from container perspective
c.DockerSpawner.hub_port = 8081        # Port of the hub API

# Docker network configuration
c.DockerSpawner.network_name = 'jupyterhub-network'
c.DockerSpawner.use_internal_ip = True

# JupyterHub configuration
c.JupyterHub.hub_ip = '0.0.0.0'
c.JupyterHub.hub_port = 8081
c.JupyterHub.hub_connect_ip = '172.18.0.1'
c.JupyterHub.ip = '127.0.0.1'
c.JupyterHub.port = 8000

Expected Behavior

I expect the configuration to be accepted without warnings, while containers properly connect to the Hub.

Actual Behavior

The setup works (containers can connect to the Hub), but I receive warnings indicating that hub_ip and hub_port are not recognized configuration options for DockerSpawner.

Questions

1. What are the current correct options to configure how containers connect back to the Hub?
2. Is there documentation for these configuration changes?
3. Do I need to update my configuration to use hub_ip_connect instead of hub_ip?

Network Debugging Info

Docker network information:

$ docker network inspect jupyterhub-network
[
    {
        "Name": "jupyterhub-network",
        "Id": "bb57a7a792ab...",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv4": true,
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": {},
            "Config": [
                {
                    "Subnet": "172.18.0.0/16",
                    "Gateway": "172.18.0.1"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": false,
        "ConfigOnly": false,
        "Containers": {
            "44852d2cd848...": {
                "Name": "jupyter-user",
                "EndpointID": "0425197c22f5...",
                "MacAddress": "7e:ac:ab:09:67:13",
                "IPv4Address": "172.18.0.2/16",
                "IPv6Address": ""
            }
        },
        "Options": {},
        "Labels": {}
    }
]

$ docker network ls
NETWORK ID     NAME                 DRIVER    SCOPE
b9e7681c91f9   bridge               bridge    local
9c2fff1a622b   host                 host      local
bb57a7a792ab   jupyterhub-network   bridge    local
8adf4715e1f7   none                 null      local

$ docker ps
CONTAINER ID   IMAGE            COMMAND                  CREATED          STATUS          PORTS      NAMES
44852d2cd848   my-scipy-image   "tini -g -- start.sh…"   54 minutes ago   Up 54 minutes   8888/tcp   jupyter-user

$ docker inspect --format='{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' 44852d2cd848
172.18.0.2

[berceanu]

Hm, it seems that just removing

c.DockerSpawner.hub_ip = '172.18.0.1'  # IP of the hub from container perspective
c.DockerSpawner.hub_port = 8081        # Port of the hub API

also works in fact, as long as I keep

c.JupyterHub.hub_connect_ip = '172.18.0.1'

However, shouldn't this IP address be detected automatically?