Skip to content

ocsp and discovery do not use lb_web network but create their own haproxy_default  #9

@BuritoSlinger

Description

@BuritoSlinger

Tried to use this to ultimately run nextcloud. I am running this on a QNAP nas box which does know about docker but does not know docker-compose ... although it is installed. So I thought I'd give it a shot.

setup lb_web worked the git worked and then:

` docker-compose up -d
Removing haproxy_ocsp_1
Removing haproxy_discovery_1
Starting haproxy_letsencrypt-web_1
Recreating 1d41a4a77454_1d41a4a77454_haproxy_ocsp_1
haproxy_letsencrypt_1 is up-to-date
Recreating 59b308ab6a62_59b308ab6a62_haproxy_discovery_1

ERROR: for letsencrypt-web Cannot start service letsencrypt-web: failed to create endpoint haproxy_letsencrypt-web_1 on network lb_web: adding interface vethe3c819c to bridge ubr-db7943c3bff failed: could not find bridge ubr-db7943c3bff: route ip+net: no such network interface

ERROR: for discovery Cannot start service discovery: failed to create endpoint haproxy_discovery_1 on network lb_web: adding interface veth65197d6 to bridge ubr-db7943c3bff failed: could not find bridge ubr-db7943c3bff: route ip+net: no such network interface

ERROR: for ocsp Cannot start service ocsp: failed to create endpoint haproxy_ocsp_1 on network lb_web: adding interface veth1c6b03e to bridge ubr-db7943c3bff failed: could not find bridge ubr-db7943c3bff: route ip+net: no such network interface
ERROR: Encountered errors while bringing up the project.`

when I check the docker network I got:
docker network ls NETWORK ID NAME DRIVER 09a0ba68ec50 bridge bridge 9633f73d5aae haproxy_default bridge c545021a49ee host host db7943c3bffa lb_web bridge 28d48d039085 none null

what am I doing wrong?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions