Build a docker image.
Adds config file .
Build cache ignores new contents.
Hours of trying to figure the shit out.
Bash into it.

GOD DAMN DOCKER HAS CACHED THE VERY FIRST VERSION OF THE FILE.

Hours lost with headcaches and thinking about existence. Fck my life.

i've been there too, and many others as well

@erandria Good to hear :)

LoL poor guy

@Reymann just use a volume, and put the conf there. or cleanup the cache. Or read the f-ing build log...
also - two stage builds.

Oh lord, I felt your pain also sometimes you are just looking at for an 🐞 with a telescope while you should've used the magnifying glass 🤷‍♂️ sometimes you walk backwards sometimes forwards

Feels like shit, but it happens to the best of us

Also, this is why I hate docker

@karma i mean, if you think about it, it's not docker's fault.

Imagine if docker erased files on host when mounting. If you bound to something like / then you would get your entire system deleted.

@magicMirror by reading the build log you mean the stdout of the build process? how would this help?

@erandria true, you are right 🤭

@erandria docker tells you which layers were built, and which ones were reused from cache. all in the build log....