Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Hmm... How about Docker with WSL1? Kind of dated, but maybe that virtual machine is more stable.. Otherwise... Maybe they can get you a server?
Just IT giving you a server and you remoting into it? The server could be Linux and you could have run all your containers on it and have your IDE's run locally.
Otherwise, what magicMirror said. If IT stops you to do what you need, make it an IT problem...
Oh, blast from the past, but a long time ago I installed docker only inside of WSL. So, no docker desktop, just install the docker Ubuntu version inside an Ubuntu wsl. That one turned out to be quite stable. You can try that. It is less complicated, since it doesn't have to connect to different wsl instances. -
@magicMirror my companies' IT gave up on this and I am probably 20 hrs deep into troubleshooting this and fed up trying to understand why software we are using does not work as it should.
-
@TrayKnots I need to be able to spin up and use containers locally as I am creating docker images and compose-files quite often.
But once more it seems Windows was the worst choice of OS I could've made.
If only unix had always had all the games, I never would have opted for Windows.
Your last suggestions sounds interesting though, I might try that.
I love docker, but when it's not working and you're having WSL permission issues on Windows, it is a pain in the ass!
I have no clue exactly why, but I tried debugging and circumventing the same problem for hours, if not days:
Docker keeps crashing due to "unexpected WSL error".
The only thing that seemed to help (sometimes, at least) was to Uninstall Docker, Reboot, Disable all Windows Feature flags that docker needs, rebooting again, enabling them flags again, rebooting, and then installing docker again.. aaaand voilá here it is again, while I almost lost all my nerves >:d
This only happens on my work-computer, which seems to not properly be connected to the ActiveDirectory Domain or something like that, which renders the whole computer basically useless and I can't do anything about it (for example, install a proper os called linux) since IT blocked BIOS access *silent cries of pain*
rant
stupid
issues
retarded
sabotage
permissions
windoof
docker
industry
wsl
bill gay
windows