Having this really weird problem.
I've got two identical ubuntu machines.They both have a CIFS share defined in /etc/fstab.
//station01/share /mnt/test cifs rw,cred=/etc/cifspasswd,forceuid,forcegid0 1
Now we run a docker image on both the machine and it gets the share passed as -v argument.
docker run --user 0:0 --rm -v /mnt/test/Target01:/workspace -w /workspace 10.203.32.90:5000/alo alo -t . project.jsonNow the weird thing is that the same process with the same args runs on machine1 but fails on machine 2!
The output of the application is that was unable to load an image with zero length name. On the other machine no error and a PDF appears on the share.
{"message":"Unable to load image ''","name":"CachedImageError" }
journalctl on the failing machine says at the point of failing:
- ubdock03 systemd-networkd[868]: rtnl: received neighbor for link '174' we don't know about, ignoring.
- ubdock03 systemd-networkd[868]: veth9159b54: Failed to wait for the interface to be initialized: No such device
- ubdock03 systemd-udevd[2710955]: veth9159b54: Failed to query device driver: No such device
While the machine that works says:
- ubdock02 systemd-networkd[913]: rtnl: received neighbor for link '491' we don't know about, ignoring.
- ubdock02 systemd-udevd[2876350]: veth186007c: Failed to query device driver: No such device
This log does not have the line
Failed to wait for the interface to be initialized: No such device
Also, the failing machine has 2 veth networkinterfaces
123: veth79feee5c@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 124:veth57e15c99@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500
The working machine has only 1
445: veth37f82759@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500
What could be wrong here or how to debug an error like this?