macvlan: failed to add interface veth4cb464e to sandbox: failed to set link up: device or resource busy

Hello

i have a big problem and hope anybody can help me.

Yesterday morning my docker node has a load avg from 50 and i got fork errors when i tried to execute commands. After service docker restart the cpu load was normal and most of my docker containers was back online, but not my gitlab server:
i tried to start the container and tried to update the container (docker stop,rm and run):
docker run -d --hostname gitlab.example.com --ip=192.168.123.123 --mac-address=00:11:22:33:44:55 --name gitlab --net=macvlanbrdige1 --publish 22:22 --publish 80:80 --publish 443:443 --restart always gitlab/gitlab-ce:latest

docker: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "process_linux.go:334: running prestart hook 0 caused "error running hook: exit status 1, stdout: , stderr: time=\"2018-09-29T20:55:34+02:00\" level=fatal msg=\"failed to add interface veth4cb464e to sandbox: failed to set link up: device or resource busy\" \n"".

if i change the mac address then i can create the container, but i want to use the "old" mac address.
docker network inspect macvlanbrdige1 shows only other containers but not the gitlab.
i think the mac address is stored by the macvlan bridge and if i know how and where i can remove the mac address, then the container will work again :)

Start with the reported docker run command and the macvlanbrdige1 output from docker network inspect, comparing the failed run using the old MAC address with the successful run using a different address. Trace how the macvlan network handles the interface and address, then determine whether the issue is a stale MAC allocation or another device-busy condition; done means explaining the cause and a reproducible cleanup or recovery path.