Published in


The gotchas in docker!

I love it. It has no doubt made my life a 1000 times easier. Want to test something out quickly in a linux machine? Spin up a container. Want to ship something out to a peer? Pack it as an image. Want to automate everything on your local? You know the answer.

So far my experience with docker has been all positive. When I say docker I literally mean docker. I have a huge respect for other containerisation engines like containerd. In fact, it is a goal for this to go full blown containerd in at least one project.

Coming back to docker — I do feel there are a few things that shouldn’t have been left unsaid. Not every dev/devops expects things to be happening in a peculiar way. The points I’m going to mention next are something that hasn’t just been noticed by me, but several other peers I interacted with:

There are a few other areas I feel things are quite surprising, but very minor ones. While I understand the issues faced by us aren’t really issues, it was quite hard to wrap our heads around the same. One way this can be tackled is better documentation, and seriously docker! The documentation needs some improvement irrespective.

That said I can’t even imagine how complicated things would have been, had docker not existed. So, thank you for that!




Encompass the correct technologies in your business and strengthen your digital presence. Our devoted software development team builds apt software and other allied services which entirely resolves your business needs

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store