Also, I don't want to have to troubleshoot why the docker daemon isn't running every time I need it
Also, I don't want to have to troubleshoot why the docker daemon isn't running every time I need it
Or so I was told when I made the monumental mistake of trying to fight such a policy once.
So now we just have a don't ask don't tell kind of gig going on.
I don't really know what the solution is, but dev laptops are goldmines for haxxors, and locking them down stops them from really being dev machines. shrug
it's pretty stupid because the same curl | bash that could have done that could have just posted the same contents directly to the internet without the container. The best chance you actually have is to do as much development as possible inside a sealed environment like ... a container where at least you have some way to limit visibility of partially trusted code of your file system.
Or when your IT department is prohibited from purchasing anything that doesn't come from Microsoft or CDW.
Where do you work ? Is that even possible in 2025?
Or so it seems to me whenever I have to deal with them. We ended up with Microsoft defender on our corp Macs even.. :|
There is no bottom to the barrel, and incompetence and insensitivity can rise quite high in some cases.