GitHub user pepdiz edited a comment on the discussion: docker installation from
github fails
thanks @dosu
I don't have any process using port 8088 but supeset itself
```
$ lsof -i :8088
$ docker ps
CONTAINER ID IMAGE
COMMAND CREATED STATUS PORTS NAMES
4d6590e8b6ea apachesuperset.docker.scarf.sh/apache/superset:latest-dev
"/app/docker/docker-…" 4 hours ago Up 4 hours (healthy) 8088/tcp
superset_worker
e166f64561d6 apachesuperset.docker.scarf.sh/apache/superset:latest-dev
"/app/docker/docker-…" 4 hours ago Up 4 hours 8088/tcp
superset_worker_beat
e1cd7455a610 postgres:16
"docker-entrypoint.s…" 4 hours ago Up 4 hours 5432/tcp
superset_db
44f5c280e679 redis:7
"docker-entrypoint.s…" 4 hours ago Up 4 hours 6379/tcp
superset_cache
```
I tried to remove supeset and install it again:
```
$ docker compose down
[+] Running 7/7
✔ Container superset_worker_beat Removed
10.2s
✔ Container superset_app Removed
0.0s
✔ Container superset_worker Removed
10.3s
✔ Container superset_init Removed
0.1s
✔ Container superset_db Removed
0.2s
✔ Container superset_cache Removed
0.2s
✔ Network superset_default Removed
0.1s
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
$ docker compose -f docker-compose-image-tag.yml up
```
but same result
```
superset_init exited with code 0
superset_worker_beat | Installing superset-core in editable mode
superset_worker | Installing superset-core in editable mode
Error response from daemon: failed to set up container networking: driver
failed programming external connectivity on endpoint superset_app
(a989a2cfc6ec7eac17633280308b727f05dd97bfbd48c0401768859cfb55e237): failed to
start userland proxy for port mapping 0.0.0.0:8088:172.18.0.6:8088/tcp: failed
to start docker-proxy, check that the current version is in your $PATH
```
again processes using 8088 are only superset ones:
```
$ lsof -i :8088
$ docker ps
CONTAINER ID IMAGE
COMMAND CREATED STATUS PORTS
NAMES
c5055dbf44ac apachesuperset.docker.scarf.sh/apache/superset:latest-dev
"/app/docker/docker-…" 2 minutes ago Up 2 minutes 8088/tcp
superset_worker_beat
f04bd06e7f66 apachesuperset.docker.scarf.sh/apache/superset:latest-dev
"/app/docker/docker-…" 2 minutes ago Up 2 minutes (healthy) 8088/tcp
superset_worker
667046ac4cef redis:7
"docker-entrypoint.s…" 2 minutes ago Up 2 minutes 6379/tcp
superset_cache
db0021980525 postgres:16
"docker-entrypoint.s…" 2 minutes ago Up 2 minutes 5432/tcp
superset_db
```
In the process of setting up the docker container I see some warnings like:
```
superset_cache | 1:C 03 Feb 2026 17:23:56.595 # WARNING Memory overcommit must
be enabled! Without it, a background save or replication may fail under low
memory condition. Being disabled, it can also cause failures without low memory
condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this
issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run
the command 'sysctl vm.overcommit_memory=1' for this to take effect.
superset_cache | 1:C 03 Feb 2026 17:23:56.596 # Warning: no config file
specified, using the default config. In order to specify a config file use
redis-server /path/to/redis.conf
superset_cache | 1:M 03 Feb 2026 17:23:56.597 # WARNING: The TCP backlog
setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set
to the lower value of 128.
superset_init | warning: Failed to hardlink files; falling back to full copy.
This may lead to degraded performance.
superset_init | If the cache and target directories are on different
filesystems, hardlinking may not be supported.
superset_init | If this is intentional, set `export
UV_LINK_MODE=copy` or use `--link-mode=copy` to suppress this warning.
```
an error about existent user: "superset_init | Error! User already exists
admin"
and even a strange message: "superset_init | Unknown Operation!!!" but
not marked as error or even warning
I think warnings may affect performance but not seem the direct cause of not
installing and running the docker container. May be a problem with trash from
previous installation?
I tried once again this time changing port to 8098 in composer file:
```
$ grep -A 1 ports docker-composeT.yml
ports:
- 8098:8088
$ docker compose -f docker-composeT.yml up
```
with the same result:
```
superset_worker_beat | Installing superset-core in editable mode
superset_worker | Resolved 1 package in 6ms
Error response from daemon: failed to set up container networking: driver
failed programming external connectivity on endpoint superset_app
(26911c804c9b9eea3cbf3a8efbe467a9fadb022f46ee7979b79473342c42dde4): failed to
start userland proxy for port mapping 0.0.0.0:8098:172.18.0.6:8088/tcp: failed
to start docker-proxy, check that the current version is in your $PATH
```
```
$ docker ps
CONTAINER ID IMAGE
COMMAND CREATED STATUS PORTS
NAMES
71f4d4a29512 apachesuperset.docker.scarf.sh/apache/superset:latest-dev
"/app/docker/docker-…" 4 minutes ago Up 4 minutes 8088/tcp
superset_worker_beat
54c497fb67c2 apachesuperset.docker.scarf.sh/apache/superset:latest-dev
"/app/docker/docker-…" 4 minutes ago Up 4 minutes (healthy) 8088/tcp
superset_worker
ccb5c0d238be postgres:16
"docker-entrypoint.s…" 4 minutes ago Up 4 minutes 5432/tcp
superset_db
afcd603d7ba9 redis:7
"docker-entrypoint.s…" 4 minutes ago Up 4 minutes 6379/tcp
superset_cache
```
Regards
GitHub link:
https://github.com/apache/superset/discussions/37610#discussioncomment-15686292
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
