rimelek
November 22, 2024, 7:26pm
7
Just becuse I noticed the similarity as well and that’s why I came here remembering this topic, I share the other one
I’m having issues with my Docker setup as it relates to networking between them. I noticed the issue by exec’ing into a container and trying to ping another container within the same Docker network.
[Screenshot 2024-11-20 at 12.17.40 PM]
Seemingly completely random packet loss. When this happens it affects all containers and all pinging/communication between containers and I cannot for the life of me figure out why, it’s almost like Docker’s internal DNS starts to die over time. Recreating a …
It is similar as it is about network connection between containers and a proxy is involved in both cases, but the error messages are different. So since I don’t have a very good idea either, I share the following issue only because you use Portainer
opened 04:55PM - 07 Oct 24 UTC
closed 06:25AM - 08 Oct 24 UTC
kind/bug
area/networking
kind/duplicate
version/27.3
### Description
Two containers got after a docker service restart the same MAC … address. This caused a lot of network issues.
it happened only twice after the restart. Not always
Containers are in the same bridge network
### Reproduce
Restart of host or docker service
### Expected behavior
Each container should have it’s own MAC address
### docker version
```bash
Client: Docker Engine - Community
Version: 27.3.1
API version: 1.47
Go version: go1.22.7
Git commit: ce12230
Built: Fri Sep 20 11:41:11 2024
OS/Arch: linux/amd64
Context: default
Server: Docker Engine - Community
Engine:
Version: 27.3.1
API version: 1.47 (minimum version 1.24)
Go version: go1.22.7
Git commit: 41ca978
Built: Fri Sep 20 11:41:11 2024
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.7.22
GitCommit: 7f7fdf5fed64eb6a7caf99b3e12efcf9d60e311c
runc:
Version: 1.1.14
GitCommit: v1.1.14-0-g2c9f560
docker-init:
Version: 0.19.0
GitCommit: de40ad0
```
### docker info
```bash
Client: Docker Engine - Community
Version: 27.3.1
Context: default
Debug Mode: false
Plugins:
compose: Docker Compose (Docker Inc.)
Version: v2.29.7
Path: /usr/libexec/docker/cli-plugins/docker-compose
Server:
Containers: 11
Running: 10
Paused: 0
Stopped: 1
Images: 11
Server Version: 27.3.1
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: journald
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
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: 7f7fdf5fed64eb6a7caf99b3e12efcf9d60e311c
runc version: v1.1.14-0-g2c9f560
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.1.0-26-amd64
Operating System: Debian GNU/Linux 12 (bookworm)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.58GiB
Name: DietPi
ID: 9fb2b93b-d4a0-470f-bfb8-c5496e5161db
Docker Root Dir: /mnt/dietpi_userdata/docker-data
Debug Mode: false
Username: wtanzer
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
```
### Additional Info
_No response_
I know it is about MAC addresses, but I wonder how you created the containers. Did you also edit or even created the containers from Portainer?