Dennis Whitney
Dennis Whitney
@dmudugamuw What are the errors? What did you change the mounts to? Volume mounts are persistent storage, so if you changed an existing setup its likely nothing is configured anymore.
In my case I can't even install from a wowinterface URL. When I feed it the URL it just says it can't be found. So far this has happened on...
Ok thanks. I'll probably just fork it and add the feature in. My situation isn't a trivial one unfortunately.
@1lann I added the feature and created a PR if you decide you want to include the feature. I'm hardly knowable in go so hopefully what I added makes sense.
Running in trace I also see that Chef reconizes that its already mounted during some evaulation. [2023-10-25T11:56:05-04:00] TRACE: Found mount /dev/mapper/my_mount to /var/lib/containers in /etc/fstab
What I added should also resolve the detection for 2.12.2 to 2.12.4 - not tested.
This issue is also problematic for conda environments.
Also to add its triggering on `/etc/cron.deny` file as well.
As anyone been able to verify this issue? I have 3 disparate clusters and a stand alone test server and they all have this issue.
This is still an issue in 3.8.0 for us.