ERROR: for grampsweb listen tcp4 bind: address already in use

OS: Mint LMDE 6
Docker-Desktop v. 4.29.0

Hi, my intention is to synchronize the Gramps root tree, using docker-compose. I don’t know if it was necessary to install docker-desktop to do this. I followed this guide from Grampsweb: The command

sudo docker-compose up -d

I was able to run it, but it has the following error message:

sudo docker-compose up -d
[sudo] Passwort für rainer:     
grampsweb_redis is up-to-date
Starting rainer_grampsweb_1 ... 
grampsweb_celery is up-to-date
Starting rainer_grampsweb_1 ... error

ERROR: for rainer_grampsweb_1  Cannot start service grampsweb: driver failed programming external connectivity on endpoint rainer_grampsweb_1 (32e874ceffa4735d0ea9f9e17cc0a5fd88534802c87c519841b39df407063124): Error starting userland proxy: listen tcp4 bind: address already in use

ERROR: for grampsweb  Cannot start service grampsweb: driver failed programming external connectivity on endpoint rainer_grampsweb_1 (32e874ceffa4735d0ea9f9e17cc0a5fd88534802c87c519841b39df407063124): Error starting userland proxy: listen tcp4 bind: address already in use
ERROR: Encountered errors while bringing up the project.

How can I solve this? Many thanks in advance for your help!

I read this thread about nearly the same issue. However, the solutions there don’t fix it here, because in my LMDE 6 there are no commands like “netsh” or “NET”.

That was a windows topic, but there are many other “address already in used” topics. Did you read this for example?

Thank you for your response. I’ve read it now. There you asked to run netstat -tulpn and for output of docker info and docker version.
Here is mine:

rainer@Optiplex:~$ netstat -tulpn
(Es konnten nicht alle Prozesse identifiziert werden; Informationen über
nicht-eigene Prozesse werden nicht angezeigt; Root kann sie anzeigen.)
Aktive Internetverbindungen (Nur Server)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0   *               LISTEN      -                   
tcp        0      0*               LISTEN      -                   
tcp        0      0  *               LISTEN      -                   
tcp        0      0*               LISTEN      -                   
tcp        0      0*               LISTEN      -                   
tcp6       0      0 :::1716                 :::*                    LISTEN      1571/kdeconnectd    
tcp6       0      0 :::631                  :::*                    LISTEN      -                   
udp        0      0   *                           -                   
udp        0      0*                           2039/vivaldi-bin    
udp        0      0*                           2039/vivaldi-bin    
udp        0      0  *                           -                   
udp        0      0 *                           -                   
udp6       0      0 :::1716                 :::*                                1571/kdeconnectd    
udp6       0      0 :::5353                 :::*                                -                   
udp6       0      0 :::60425                :::*                                -                   
rainer@Optiplex:~$ docker info
Client: Docker Engine - Community
 Version:    26.1.1
 Context:    desktop-linux
 Debug Mode: false
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.13.1-desktop.1
    Path:     /usr/lib/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.26.1-desktop.1
    Path:     /usr/lib/docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container. (Docker Inc.)
    Version:  0.0.27
    Path:     /usr/lib/docker/cli-plugins/docker-debug
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     /usr/lib/docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.23
    Path:     /usr/lib/docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.4
    Path:     /usr/lib/docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.1.0
    Path:     /usr/lib/docker/cli-plugins/docker-init
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /usr/lib/docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.6.3
    Path:     /usr/lib/docker/cli-plugins/docker-scout

 Containers: 1
  Running: 1
  Paused: 0
  Stopped: 0
 Images: 1
 Server Version: 26.0.0
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
 runc version: v1.1.12-0-g51d5e94
 init version: de40ad0
 Security Options:
   Profile: unconfined
 Kernel Version: 6.6.22-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 6
 Total Memory: 7.518GiB
 Name: docker-desktop
 ID: 5275a71b-5994-4ad5-8784-1d130e23b9a4
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Experimental: false
 Insecure Registries:
 Live Restore Enabled: false

WARNING: daemon is not using the default seccomp profile
rainer@Optiplex:~$ docker version
Client: Docker Engine - Community
 Cloud integration: v1.0.35+desktop.13
 Version:           26.1.1
 API version:       1.45
 Go version:        go1.21.9
 Git commit:        4cf5afa
 Built:             Tue Apr 30 11:48:28 2024
 OS/Arch:           linux/amd64
 Context:           desktop-linux

Server: Docker Desktop 4.29.0 (145265)
  Version:          26.0.0
  API version:      1.45 (minimum version 1.24)
  Go version:       go1.21.8
  Git commit:       8b79278
  Built:            Wed Mar 20 15:18:01 2024
  OS/Arch:          linux/amd64
  Experimental:     false
  Version:          1.6.28
  GitCommit:        ae07eda36dd25f8a1b98dfbf587313b99c0190bb
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
  Version:          0.19.0
  GitCommit:        de40ad0

So, I now have this output:

rainer@Optiplex:/var/www/html$ docker-compose up -d
grampsweb_redis is up-to-date
grampsweb_celery is up-to-date
html_grampsweb_1 is up-to-date

On this page it is said that

On first run, the app will display a first-run wizard that will allow you to

Create and account for the owner (admin) user
Set some necessary configuration options
Import a family tree in Gramps XML (.gramps) format

However, I don’t get this first-run wizard. How can I open it?

Since you run the containers in detached mode, you won’t see anything. Everything is in the logs.

docker compose logs

Thank you!
There are some repetitive messages in the log. I don’t want to post everything here, only if necessary. In the following example there are 2 problems at the same time:

/usr/local/lib/python3.11/dist-packages/gramps/plugins/tool/ PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.
html_grampsweb_1  |   from gi.repository import Gtk

The directory /usr/local/lib/python3.11/dist-packages/ is empty. I can’t find the gramps folder or celery and its subfolders there. I can’t figure out how to load the correct gtk version.

How can I repair it?

I found out today that instead of
there is

The used path was wrong then. However, I don’t know and can’t find out, what caused to use wrong paths.

I wrote an issue at Github/Gramps.

This could explain the role of the different folders

Thank you again for your response. I learned that it could be an issue using “sudo” or not. Concerning this Gramps related issue I don’t remember coming across that. Maybe I used “sudo docker-compose up -d” in the beginning? Don’t know exactly but I think no, I don’t. Just copied the command as it is displayed there - without “sudo”.

Do you think that bringing this issue to Github/Gramps is the right way addressing it for getting a solution?

Since we are talking about python packages in the container, it doesn’t matter how you ran docker compose. That could only change which Docker context you use, not which folder you use inside the container.

OK, got it. Is it then the only conclusion that something went wrong caused by Grampsweb install procedure?
I’m not a programmer. I thought just follow the instructions as usual…

We started the discussion about used ports. I could reply to that. I can’t tell what went wrong with Python. It could be an issue with the image or with how you followed the instructions. Unfortunately I don’t have time to test every image, but If the image maintainers can’t find the issue, I recommend opening a new topic here, because nobody will answer if they don’t even know from the title that they could.

I appreciate how you comment this and will open a new topic if needed. Thank you so much for your help!