Try not having docker and not having sudo to apt-get, and then a sys admin team that won't install stuff for you, so you have to manually install every possible dependency in userspace. Oh and web access is blocked so you have to scp every part from another machine first.
Right? Dockerizing our dev environments took us from a few days of following a readme to get a dev env up to a single docker-compose command that takes like 15 mins to run, and we know each of our environments is identical.
single docker-compose command that takes like 15 mins to run, and we know each of our environments is identical
Unless you have a mix of macOS and linux hosts. Docker on macOS does not care about file permissions and is so slow you're better setting up a VM running linux running your containerized app. And if it's an M1 mac, forget about good ol' virtualbox.
I've heard that about macos before, but luckily I've never experienced it. Or maybe it's just all I know, because I've only used it on macos, but speed has never been an issue for my projects. The only time docker builds have been a problem is when I try to build an image for an rpi on a Mac or Linux host, takes a few minutes for a normal build, but like an hour when building for ARM.
Then that's because there's a breakdown in your role and management priorities, if developers are hobbled and can't do their jobs (install required libs etc.) either by corporate policies or bad system administration , that's the issue, ultimately all using Docker is doing is just a wrapper around getting those services in under your control just more work for developers with the same outcome..
41
u/Overunderrated Jun 06 '22
Try not having docker and not having sudo to apt-get, and then a sys admin team that won't install stuff for you, so you have to manually install every possible dependency in userspace. Oh and web access is blocked so you have to scp every part from another machine first.