Check out my current scenario:

I have to show some progress in fixing a bug to management in the morning..

I tried to sleep early, so that I cud fix it before the standup..

but I couldn't sleep, so I thought of fixing the issue now itself..

Sat down to fix, got stuck with a stupid blocking issue, did all the wrong things to debug it, wasted 3 hours, found the issue fix (not related to the main bug at all)

nd now going to sleep..

It's like:
Distance covered = 1000kms
Displacement = 0!!!!

For anyone wondering, our NodeJs application creates docker container using the '--rm' flag, it moves the whole server code to the container(including the node_modules), for some reason my package-lock.json was modified which required "npm install" (otherwise it works without that) before running server.js

So the docker container was failing, and because of the '--rm' flag the container gets removed without a trace. And in the NodeJs application it was showing that the container was successfully created and running, but I couldn't see it using "docker ps".

Nd for some fucking reason I went through the most stupidest ways of debugging it.. 🤦🏽‍♂️

Anyways gotta sleep now!

Mate that sucks haha
But why run the rm flag when you’re still building the container. At least bind the logs to the host or something

Showing some progress to management is a social skill mostly unrelated to coding and actually solving problems. I used to speak up on behalf of junior coworkers and try to make it clear what kind of challenges made our work take longer than expected but what a great business value will result when we finished.

@Chewbanacas not really familiar with docker that much, but shouldn't they do that by default?

Thank god there was docker "events", which told me that the container was getting destroyed as well.

At a point I even thought I had some hackers interfering with my setup.. 🤣 it's better I shut up nd get that sleep next time..