Docker's autobuilt images randomly don't work.

[Galaxxius]

Docker Image is broken. If you try running it, it complains that the front end assets are missing and the user should run non install.

[Galaxxius]

*npm install

[sebastienvercammen]

Someone else had this same issue, except that the image was constantly being rebuilt after each commit by Docker and 2 out of 3 images worked while the third didn't work. For no reason whatsoever, as none of the commits changed the build process, requirements, ... or anything related.

Pinging @FrostTheFox Foxbabe on this to take a look. 🤷‍♂️

[Galaxxius]

following your hint I cloned the repo and built the image myself without any changes - and guess what, it worked. The result of the build is equivalent to the image on dockerhub - which does not work @_@

[sebastienvercammen]

@Galaxxius Thanks for the update. I've changed the title and tags so we can take a look at what's going.

[dannythunder]

my workaround is to build outside docker first. Annoying.

[FrostTheFox]

I have no knowledge of docker and I've been considering it unsupported. It was simply a migration from the old namespace. I see npm run build in the run portion of the dockerfile, so I assume that would take care of things, but I guess something isn't working properly in these instances. If anyone has any ideas feel free to chime in.