4 ms·
Disclaimer: I would consider myself one of the developers who tries docker out every couple of years, but just can't seem to get it. > the developer environmen
by tony 7y ago
Disclaimer: I would consider myself one of the developers who tries docker out every couple of years, but just can't seem to get it.
> the developer environment just doesn’t square well with whatever system is running your code. In the olden days of yore, this disparity was so great that we often had to tunnel in to an environment that was exactly like our production server
For web apps, I've gotten stuff working very easily across linux, freebsd, and mac os. Thanks a lot due to package managers, up to date library packages, and any python/ruby/node packages with c/c++ parts generally being able to find the header/.so files. Lockfiles (package-lock.json, poetry.lock) have gotten better as well, so I feel secure knowing that there won't be hiccups there.
Thank you for your comment on docker CLI.
I find docker commands more confusing and obtuse to work with than the commands of postgres, python, node, webpack, combined. All of them. Because it's about having to think about copying files, proxying against the file system, layers of containers. By the time stuff is running I feel so far away from the roots, I'm asking myself how much of a favor is this really doing?
The other thing is deploying these images is a lot of work compared to just running SSH commands via fabric, pulling code, and restarting services. I also think developers benefit from jumping in and wiring in the daemons themselves on whatever system. I think it's part of what fullstack is. It'll come in useful should stuff go wrong in production.
I also found my experimentation with docker inconsistent, even when I cloned projects from git repos with docker compose, I have a high failure rate. To the point I'd be happier if they just gave instructions for me to wire in the daemons and db myself. And when I google, I go down a rabbit hole of configurations and github issues that don't seem to fit (perhaps docker or docker-compose is out of date somehow? Or is it the project itself? Or me?)
- sk5t 7y agoI didn't really buy wholly into containers for a while either, but the tools have gotten better, the process makes it easier to tick the security boxes, and the confidence brought about by immutable deployments and having good visibility into the service state has been really valuable in a growing environment. No more "oh yeah, we poked at ulimit on that server late Friday night, that's why the other ones don't work as well" and so on. No fiddling around with multiple python or java environments. Keep after the details and you can end up not even having anything to ssh into at all--really get out of the game of "server touching" if you will.