Bridge networks are usually used when your applications run in standalone containers that. If you don’t specify a driver, this is the type of network you are creating. Several drivers exist by default, and provide core networking functionality: bridge: The default network driver. "Driver": "default", "Driver": "default", Docker’s networking subsystem is pluggable, using drivers. "EnableIPv6": false, "EnableIPv6": false, "Name": "activemq_default", | "Name": "bridge", There is no custom docker network or configuration defined. My question is: why would this behaviour occur, and how can I troubleshoot this? Other containers seems to behave fine, including port forwarding. When I manually prepare the container's configuration and modify the default `0.0.0.0` to `127.0.0.1`, for the websocket server, the error does not occur anymore.
It is the one for WebSockets that fails, on 0.0.0.0:61614, which apparently is resolved to an attempted bind on olympos:61614. The activemq configuration defines binds on 0.0.0.0 for various ports. The strange thing here is that `olympos` is the hostname one of my local machines, which is also hosting my DNS server (pihole). The last one fails (WebSockets), which tries to bind to `olympos`. Note that all port binds succeed, using the container's hostname (4a4.54e). : Cannot assign requested addressĪt .Net.bind0(Native Method)Īt .Net.bind(Net.java:433)Īt .Net.bind(Net.java:425)
WARN | FAILED : Cannot assign requested address WARN | has uncovered http methods for path: / INFO | Listening for connections at: mqtt://4a415e89a54e:1883?maximumConnections=1000&wireFormat.maxFrameSize=104857600 INFO | Listening for connections at: stomp://4a415e89a54e:61613?maximumConnections=1000&wireFormat.maxFrameSize=104857600 INFO | Listening for connections at: amqp://4a415e89a54e:5672?maximumConnections=1000&wireFormat.maxFrameSize=104857600 JENKINS_JAVA_OPTIONS="=true =\"default-src 'self' 'unsafe-inline' 'unsafe-eval' img-src 'self' 'unsafe-inline' data: \""
0 kommentar(er)
