I like to validate stuff in Docker. Think CI. Transparently testable, and as a side product a publicly verifiable set of software for later reproducibility. Archive the container image as tar for (far) future reference when remote repositories or dependencies are deleted.
-
-
-
Oh yeah, for CI, it’s great. But as a dev environment, the whole experience is terrible.
End of conversation
New conversation -
-
-
But I thought the point was that via docker, everything becomes native-ish?
-
Yeah, right.
End of conversation
New conversation -
-
-
Main disadvantage of Docker is IMHO the mess with virtual network interfaces and especially iptables it introduces.
-
Not to mention that on MacOS, Docker for Mac is slow as fuck.
- 1 more reply
New conversation -
-
-
every python "coder" say this. It's a poc hat your tool can get build and deployed on fresh.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
IMHO docker is not done for that actually... I personally patch my /etc/hosts with container ip and name (via docker events script) and my IDE and tooling communicate via their name. Every tcp ip based tool can use this trick. We have 12+ of products with subtle config variations
-
Moreover, because we have dependency between services hosted in different products. It easy to "mock"/proxy a dependency in dev to a server in staging env via dockerized socat. As I see it, Docker is lightweight & nice for
#livingDocumentation but bad substitute for DevOps. - 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.