5

Hell of a Docker

One application in c++. 4 in c# targeting Linux. Several logging places, Several configuration files , dozens of different folders to access (read/write). Many applications being called from just one that orchestrates everything.

OS is Linux. Installation is to be made inside a docker image and later placed in a container by means of several bash files and python scripts. All these are part of a legacy set of applications.

They’ve asked me to just comment out one line which took 3 days to find out because they didn’t remember where it was and in which application it was and what was in that line.

After changing it, I was asked to create a test environment which must have resemblance to the current server in production. 12 days later And many errors, headaches, problems with docker, I got it done.

Test starts and then, problems with docker volumes, network, images, docker-composer, config files and applications, started to appear.

1 month later, I still have problems and can’t run all applications at least once completely using the whole set.

Just one simple task of deploying locally some applications, which would take one or two days, is becoming a nightmare.

Conclusion: While still trying to figure out why an infinite loop was caused by some DB connection attempt in an application, I am collecting a great amount of hate for docker. It might be good for something, that’s for sure, but in my experience so far, it is far worse than any expectations I had before using it.

Lesson learned: Must run away from tasks involving that shit!

Comments
  • 9
    This sounds like a company using docker without knowing what the actual fuck docker is. If anything docker should relieve you from additional deployment problems, not create new ones.
  • 2
    Geez someone setup docker in a most disorganized fashion I have ever heard of
  • 2
    It's not a docker's fault. It's their apps
  • 0
    Docker is supposed to help not create a new problems, if you don't really need it it doesn't have sense to add additional technology to workflow.
  • 0
    Every application should have been a container. Every technology stack should have been a container.
    It sounds like they are using docker like a VM.

    If you can’t turn the container off and on again without problems they are using docker wrong.
Add Comment