Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Yeah but some of us have paid those dues over time and don't have that level of issue with Docker any longer.

I used to really struggle getting Docker and docker-compose to do what I want, but after a few years working with it, I'm not blocked by the various volume or network or what-have-yous that used to come up.

Alternative proposal: run your containers in docker-compose environments on an ec2 instance. Everyone wins?



If it takes years to figure out how to do things "properly" with Docker, then maybe it isn't very good.


Maybe, but now that I have, it's very very good.

It's also totally reasonable to say, "It shouldn't have taken you years." It probably shouldn't have!


We started that way. I'm honestly surprised this isn't suggested more often. It allowed our devs to benefit from containers while not totally uprooting our existing Infrastructure.

We've mostly moved to EKS now but we had plenty of time to do it right thanks to this approach.


How would you handle ci/cd with docker compose on an ec2 instance?


Depends on... literally everything about your infrastructure. All kinds of options, pretty much anything is possible here, depending on what you want to do.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: