Docker Community Forums

Share and learn in the Docker community.

Cant create macvlan network container error

The host has assigned multiple IP addresses that I will use to assign to the container,after running for some time, there was a problem today, unable to access container independent IP.

Rebuild the container as before, prompt

docker: Error response from daemon: OCI runtime create failed: container_linux.go:345: starting container process caused "process_linux.go:430: container init caused \"process_linux.go:413: running prestart hook 0 caused \\\"error running hook: exit status 1, stdout: , stderr: time=\\\\\\\"2019-09-14T07:29:36-04:00\\\\\\\" level=fatal msg=\\\\\\\"failed to add interface vethb209404 to sandbox: error setting interface \\\\\\\\\\\\\\\"vethb209404\\\\\\\\\\\\\\\" MAC to \\\\\\\\\\\\\\\"02:42:67:65:df:03\\\\\\\\\\\\\\\": address already in use\\\\\\\"\\\\n\\\"\"": unknown.

Client:
Debug Mode: false

Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 2
Server Version: 19.03.2
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 894b81a4b802e4eb2a91d1ce216b8817763c29fb
runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f
init version: fec3683
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.19.0-5-amd64
Operating System: Debian GNU/Linux 10 (buster)
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 15.63GiB
Name: debian2
ID: 3OHD:FAOC:LHIA:QU23:H47U:7SVT:2ZRA:GEEO:VLDQ:V4CG:VDFZ:LHH4
Docker Root Dir: /var/lib/docker
Debug Mode: false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false

WARNING: No swap limit support

Please share the complete command or compose.yml that was used to create the container(s).

I don’t know what happened. When I asked the host, they told me that there is no limit to the IP assigned to me

I solved this problem because the host only grants the IP address to the trusted MAC address. So I can’t bind the IP to the docker with other MAC addresses.

Hello nishuo may I know how did you solve this issue, as I am also facing the same issue