Hi, couldn't find (pun intended) anything related to this in the changelog. As you might have guessed already the best thing to see if this is related to busybox or not, is to run the same version as you do on your local workstation. Containers are kinda creepy since they may exposé a different filesystem within themselves. If you don't have a bug in latest busybox on your local workstation but the latest busybox gives an error within you container, I'd say it's not a bug per se in busybox. Or, worse, if there is an error; it's interesting to find the root cause of the different behaviors. How is the 'findutils' "find" behaving in the same environment? What filesystem is used? //Markus Sent from my BlackBerry - the most secure mobile device
I'm having a weird issue with find outputting strange paths when there are symlinks in the directory. In a directory /foo/bar with a link "baz" to "..data/baz", `find /foo/bar -type f` outputs something like /foo/bar/..2020_09_21_21_23_25.153608192/baz find /foo/bar without predicates returns /foo/bar/baz # <- this is what I'm trying to get /foo/bar/..data # <- not these /foo/bar/..data/baz # <-/ This is happening in a container on Kubernetes, with busybox 1.30. I don't have this problem on my local workstation, without docker involvement but busybox 1.31. Is this a known issue? -- Judson Lester | ||
_______________________________________________ busybox mailing list busybox@busybox.net http://lists.busybox.net/mailman/listinfo/busybox
