75beca22a5
Symlinks inside of the chroot were failng because we weren't able to determine if they were pointing to a real file or not. We could write some complicated code to walk the symlink path taking into account where the root of the tree is but that could be fragile. Since this is just a sanity check, instead we just assume that the chroot is fine if we find that /bin/sh in the chroot is a symlink. Can revisit if it turns out that many chroots have a /bin/sh that's a broken symlink. Fixes #16097 |
||
---|---|---|
.. | ||
ansible |