[Pavel Mironov]

:/opt/otobo-docker# docker-compose up –detach
otobo_redis_1 is up-to-date
otobo_db_1 is up-to-date
otobo_elastic_1 is up-to-date
Starting otobo_web_1 …
Starting otobo_web_1 … error

ERROR: for otobo_web_1 Cannot start service web: failed to set up container networking: driver failed programming external connectivity on endpoint otobo_web_1 (80166afb97995ffba0d54313833597e9d998047e7d9ab3d78c8ca2693831d96b): failed to bind host port for 0.0.0.0:80:172.18.0.5:5000/tcp: address already in use

ERROR: for web Cannot start service web: failed to set up container networking: driver failed programming external connectivity on endpoint otobo_web_1 (80166afb97995ffba0d54313833597e9d998047e7d9ab3d78c8ca2693831d96b): failed to bind host port for 0.0.0.0:80:172.18.0.5:5000/tcp: address already in use
ERROR: Encountered errors while bringing up the project.

:/opt/otobo-docker# ss -tulnp
Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
udp UNCONN 0 0 0.0.0.0:5353 0.0.0.0:* users:((„avahi-daemon“,pid=593,fd=12))
udp UNCONN 0 0 0.0.0.0:51241 0.0.0.0:* users:((„avahi-daemon“,pid=593,fd=14))
udp UNCONN 0 0 [::]:5353 [::]:* users:((„avahi-daemon“,pid=593,fd=13))
udp UNCONN 0 0 [::]:40153 [::]:* users:((„avahi-daemon“,pid=593,fd=15))
udp UNCONN 0 0 [fe80::67c:16ff:fe72:ebac]%enp37s0:546 [::]:* users:((„NetworkManager“,pid=637,fd=28))
tcp LISTEN 0 20 127.0.0.1:25 0.0.0.0:* users:((„exim4“,pid=1602,fd=4))
tcp LISTEN 0 128 127.0.0.1:631 0.0.0.0:* users:((„cupsd“,pid=704,fd=7))
tcp LISTEN 0 20 [::1]:25 [::]:* users:((„exim4“,pid=1602,fd=5))
tcp LISTEN 0 128 [::1]:631 [::]:* users:((„cupsd“,pid=704,fd=6))
tcp LISTEN 0 151 *:3306 *:* users:((„mysqld“,pid=971,fd=23))
tcp LISTEN 0 70 *:33060 *:* users:((„mysqld“,pid=971,fd=18))
tcp LISTEN 0 511 *:80 *:* users:((„/usr/sbin/apach“,pid=814,fd=4),(„/usr/sbin/apach“,pid=813,fd=4),(„/usr/sbin/apach“,pid=812,fd=4),(„/usr/sbin/apach“,pid=811,fd=4),(„/usr/sbin/apach“,pid=810,fd=4),(„/usr/sbin/apach“,pid=808,fd=4))

Help me! :)

[Pavel Mironov]

11.0.1

:/opt/otobo-docker# docker-compose up –detach
otobo_redis_1 is up-to-date
otobo_db_1 is up-to-date
otobo_elastic_1 is up-to-date
Recreating 2c8924235899_otobo_web_1 … error

ERROR: for 2c8924235899_otobo_web_1 No such image: sha256:2e160a91ed92809b8462e3a27e9124a57ad3cf1851b82739fb91f77ebae0e55d

ERROR: for web No such image: sha256:2e160a91ed92809b8462e3a27e9124a57ad3cf1851b82739fb91f77ebae0e55d
ERROR: The image for the service you’re trying to recreate has been removed. If you continue, volume data could be lost. Consider backing up your data before continuing.

Continue with the new image? [yN]
ERROR: No such image: sha256:2e160a91ed92809b8462e3a27e9124a57ad3cf1851b82739fb91f77ebae0e55d

[Pavel Mironov]

Debian 12

[Mike Thumes]

Hi Pavel, hope you’re fine.

looking at your first post it looks like you are already running a local apache httpd server on Port 80, and then try to run otobo-docker, which by default also tries to bind port 80 for its nginx instance, causing the conflict.

Things to try: Either shutdown the apache server first and try again, or modify the public HTTP port for otobo-docker – for the latter please have a look at your .env file in the otobo-docker root folder and modify the OTOBO_WEB_HTTP_PORT and/or OTOBO_WEB_HTTPS_PORT variables.

The second one looks strange, looks like some problem with downloaded images (or have you modified the images as well?).

Things to try: run docker compose pull in the otobo-docker folder, which should bring downloaded images to the newest version. If the error persist try to clean up your local docker cache with https://docs.docker.com/reference/cli/docker/image/prune/ .

Hope this helps!

kind regards,
-mike

• Diese Antwort wurde vor 1 Woche, 3 Tage von Mike Thumes geändert.

[Autor]

Beiträge