I have issues with Docker a lot. Example: Rename a file from “File.js” to “file.js” in a dependency and it’s like something caches the old name so even when I redownload or install that dep it tries the old name and fails to find the file. Might just be me and my tomfoolery
if you’re renaming from File.js to file.ts, which is also changing suffixes instead of just capitalization, then that couldn’t be explained by case sensitivity, unless it was a typo and you meant File.js to file.js
This is likely because docker runs Linux in a VM on MacOS right?
We’ve had similar problems with stuff that works on the developers Mac but not the server which is case sensitive. It can be quite insidious if it does not cause an immediate “file not found”-error but say falls back to a default config because the provided one has the wrong casing.
Yeah exactly. And I mount the volume to the local directory so they try to sync both ways. It’s a real mess. The solution is currently to: not fuck up the file name casing in the first place. lol
The same issue happens with git (on windows). The file system says they’re the same file and they haven’t changed, so you have to manually tell the program the file changed. With git, you’d run git rm --cached && git add. On docker, you could just do a non-cached build via docker build . --no-cache
I have issues with Docker a lot. Example: Rename a file from “File.js” to “file.js” in a dependency and it’s like something caches the old name so even when I redownload or install that dep it tries the old name and fails to find the file. Might just be me and my tomfoolery
if you’re renaming from
File.jstofile.ts, which is also changing suffixes instead of just capitalization, then that couldn’t be explained by case sensitivity, unless it was a typo and you meantFile.jstofile.jsYep typo thanks
This is likely because docker runs Linux in a VM on MacOS right?
We’ve had similar problems with stuff that works on the developers Mac but not the server which is case sensitive. It can be quite insidious if it does not cause an immediate “file not found”-error but say falls back to a default config because the provided one has the wrong casing.
Yeah exactly. And I mount the volume to the local directory so they try to sync both ways. It’s a real mess. The solution is currently to: not fuck up the file name casing in the first place. lol
The same issue happens with git (on windows). The file system says they’re the same file and they haven’t changed, so you have to manually tell the program the file changed. With git, you’d run
git rm --cached && git add. On docker, you could just do a non-cached build viadocker build . --no-cache