3 ms·
I started working with a company a little over a month ago. They "kind of" containerized the different parts of their stack. They don't use the dockerized versi
by geuis 11y ago
I started working with a company a little over a month ago. They "kind of" containerized the different parts of their stack. They don't use the dockerized versions in production. I have been the only engineer actually trying to make this work. Its been a nightmare.
Getting setup: They have about 15 parts of the application stack. When trying to get everything up and running, each layer was anywhere from 15mb to 100mb and so we're talking several gb of Docker layers just to get the basic stack in place. Then the configurations were all over the place and nothing was quite documented right.
Then it turns out there is not any clearly defined, standard way to do local development out of Dockerized applications. So I end up having to run the parts of the site I'm working on locally, and then had to configure them extra to talk to the docker-hosted parts.
So now I'm working with this hodgepodge setup that mostly works, except when it doesn't. On 2 Fridays in the last month, oddly 2 weeks apart, my Docker environment has just eaten itself and I've been forced to rebuild it. The first time some space requirement got hit and the images got corrupted. Then last Friday virtualbox was having some freakout and started pegging at 100% cpu usage before again, everything got corrupted. Now its Monday and I'm trying to put this back together again a 3rd time.
I want this to work but its just been the most frustrating onboarding experience of any company I've worked at.