Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Except that they fucked up licensing, platform support and further development, yes.
Demolishun22978326dIs Kuber a better Docker? Clueless on these machine packaging techs.
@preezer docker desktop on windows is licensed.
Plus that the Windows version was preconfigured with Buildkit and experimental features since v19.X I think. Whole lot of funny breakage thx to these stupid mofos...
Further development is bit more complicated...
In a nutshell, docker compose exists in V2 as a separate package:
Which breaks things. Which could be good if they did it ... Right?
But it isn't right. Docker compose v2 is integrated into Mac / OS docker packages, which brings me back to point 1.
They integrated a wrapper / shim to translate from v1 to v2 .
Which gave us some more funny headaches at some places, as the underlying tech stack is entirely different - Python vs Go.
Meaning that handling of TLS and everything else is entirely different...
Last but not least, look at the changelog / release notes.
Docker V2 had in the last versions many broken shit. Like really broken broken broken broken shit.
It was an pre RC labeled as general availability with a shim for v1 to be with halfbaked stuff all over and piles of poo put in between.
I'm still not happy with the quality, but we found enough workarounds for it to not explode in our faces anymore.
lorentz12028326dI love docker but the fact that BuildKit's features weren't included from the get go and Docker can't be told to follow symlinks is incredibly stupid. With pre-buildkit docker a file belonged to exactly one container, and containers were always meant to be units of execution, a bit like processes. I have yet to see a project where every file belongs to exactly one process.
spongegeoff742326dDocker is one of my pet hates. Along with anything else that adds a bucketload of complexity for no obvious gain.
I'm not entirely sure what you mean.
But maybe as an explanation... We don't have "one developer"… and not just "one docker server".
I guess that's true for any larger company.
And unless you really want to babysit the devs and explain them every click cause ... They're to dumb to shit.... You'll have to expect a certain variance of versions, clients etc.
Which is usually fine cause most programs don't shit on interoperability (regressions aside).
That's the point - docker broke interoperability.
What hurts especially is that our scenario is really pretty common if you have old docker deployments, which cannot be migrated without huge effort.
So think more 50 plus devs which all are opinionated and biased and roughly 20 ... 30 ? I think docker hosts for deployment.
Deployments. Don't know a number. Many. XD
darksideofyay5396324dthe concept of virtual workspace is really neat, but Docker makes me kinda worried. They look like that kind of business that get people dependent on their product and then put a pay wall later on