3 ms·
Some good points. One I liked was... "However, when you consider the hoops you have to jump through to use Docker from a Windows machine, anyone who tells you
by mcguire 9y ago
Some good points. One I liked was...
"However, when you consider the hoops you have to jump through to use Docker from a Windows machine, anyone who tells you that Docker simplifies development on a Windows machine is clearly joking with you."
(By the way, can anyone give me the 20 second version of how to get a container to be able to talk to an existing remote database?)
On the other hand, his comments on language seem... schizophrenic. Some other languages are not "cloud ready", but Go is? Python has always had a concurrency thing, but jumping on Go or Elixir and expecting the magic fairys to come out of the walls and fix your stuff is delusional.
- sundvor 9y ago1) I didn't get the Windows thing. Maybe I'm just using it too simply? 2) Existing remote db: I haven't tried, but recently came across docker 'run --net="host"' when finding host.docker.internal as how to access services running on the host from the docker image. Would that do the trick? https://stackoverflow.com/questions/24319662/from-inside-of-a-docker-container-how-do-i-connect-to-the-localhost-of-the-mach https://stackoverflow.com/questions/24319662/from-inside-of-...
- Too 9y agoNet=host basically defeats most benefits of network isolation you get with docker. It should only be used for quick hacking. Use forward and reverse args instead. And as others said, connecting out from the container is possible by default, with the only confusion that localhost might not be what you think.
- sundvor 9y agoAhh, very good, appreciate that.
- AlexCoventry 9y agoI'm quite intrigued by his other essay, "Docker protects a programming paradigm that we should get rid of"[0], because I am very much embedded in that paradigm, and while I think I have a working understanding of modern concurrency frameworks from using clojure's core.async, I don't really see where docker fits into the protection of the old way. [0] http://www.smashcompany.com/technology/docker-protects-a-programming-paradigm-that-we-should-get-rid-of http://www.smashcompany.com/technology/docker-protects-a-pro... On the other hand, it's been clear to me almost from when I started using it that docker is great for development, but likely to cause huge headaches in production. It occasionally behaves in weird ways I can't explain, which is fine during development, but a would potentially be showstopper at scale.
- ofrzeta 9y agoUsing a remote database should work out of the box assuming you didn't change the default network or security.
- jjeaff 9y agoThat's what I was thinking. Docker doesn't block outgoing ports. So connect to whatever external database you want, the same way you connect with any other external server.
- lmm 9y ago> Some other languages are not "cloud ready", but Go is? Python has always had a concurrency thing, but jumping on Go or Elixir and expecting the magic fairys to come out of the walls and fix your stuff is delusional. Python's packaging story is just remarkably awful. Every few years we hear about a new packaging format or tool or database that will fix everything, for real this time, and it turns out to be just one more failure on the pile. This is what the author means about not being "cloud ready": it's just way too hard to get a python-as-it's-actually-used (i.e. with a bunch of native C extensions that rely on system shared libraries for their functionality) service packaged up so that you can deploy it to some random server and be confident that it will work right. It's not that Go or Elixir have magical fairy dust, they've just managed not to screw it up.
- darkarmani 9y agoWhat about conda? Now the anaconda distribution packages up everything including c-libraries into your conda environment to isolate you from the host libraries.