Jason Cox
Jason Cox
Still running into this issue. @pschichtel could you provide a quick example of loading the plugin on the root project without applying it?
We create a selinux policy to make it work. I don't remember how we figured this out, but we have our ansible do it automatically now. 1. Create `/root/localpathpoicy.te` ```...
Another +1 for this, without it scans do not work on nodes that are tainted for specific workloads.
Another issue here with the same problem https://github.com/nodesource/distributions/issues/1653
I would really like to see this move forward also, it's very unintuitive to have to set this manually in the code.
This really need to be fixed
Is there a tentative date for when the new image will be ready?
@rsenden Thank you for posting this information, it saved me hours of time trying to figure this out. I recently just switched from a `UnifiedLoginToken` to a `CIToken` and suddenly...
Installing the `community.docker` collection at 3.10.2 manually before running molecule seems to work around the issue. Molecule doesn't force downgrade thankfully.
This is one of the main reasons we switched to longhorn. Local path really isn't useful beyond testing.