I have a debian docker host that runs these docker containers: swag: reverse proxy for jellyfin, and manages https certs. Connected to a user-defined bridge. jellyfin: accessed behind reverse proxy via a subdomain. Connected to the same user-defined bridge as swag. Timeline: Aug ~15 to 31: Can’t access jellyfin from WAN. Can access jellyfin from ..
I have a VM with a docker running, on dmesg i see somme errors: Messages “promiscuous mode” entered & left Can you help me to resolve the issue? Thank you. Source: Docker..
I want to create docker bridge network where I can place containers without internet access but access to each other. How would i go about configuring this? Source: Docker..
On a fresh debian 10 server I installed docker-ce engine 20.10.6. Even with a simple alpine instance I can’t make a network connection to outside the container. I followed the steps according to https://docs.docker.com/network/network-tutorial-standalone/ So it should work. But it doesn’t. Can someone give me a clever hint? The steps are the minimum to reproduce ..
i have tried all of thes solutions to change the ip-address of my bridge: Change default docker0 bridge ip address But i allways got thes error: ● docker.service – Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2021-07-10 20:02:29 CEST; 9min ago Docs: https://docs.docker.com Process: 3130 ..
I have mounted two identical docker on two ubuntu vps with docker-compose. The concern is that the first one works well, and the pilces dialogue between it, the second one not. What I see is that the ip set by default in 1 / is 172.X.X.X and the one set in 2 / is 192.X.X.X. ..
I am having 10 Dockers running in production environment all are talking to each other using a docker bridge that I defined, everything works great till you restart the production server. Post restart the bridge IP address to docker containers changes and Dockers are no longer able to communicate with each other. As the IP ..
I have a linux network bridge which has 2 ports attached to the docker containers. Create Containers (c1 & c2): docker run -d –cap-add NET_ADMIN –privileged –name c1 -i -t –network none baseimage:latest bash docker run -d –cap-add NET_ADMIN –privileged –name c2 -i -t –network none baseimage:latest bash Create Linux Network Bridge: ovs-vsctl add-br sw1 ..
I’m running a dockerized GitLab instance with "userns-remap" enabled and I’d like to use a shared PostgreSQL on the host. The bridge created when I docker-compose up, however, gets a new random name "br-xxxxxxxxxxxx" on every run. This wouldn’t usually be a problem, but the Vuurmuur firewall on the host blocks all traffic from the ..
docker network create with the bridge driver creates an actual bridge device on the host machine. I’m adding the host NIC into the bridge eth0 (to achieve something similar to virtual machines bridge mode). As with any bridge, when that happens, host eth0 configurations, do not apply anymore, rather the docker-created network bridge interface is ..