[BUG] 'latest' is pointing to pre-releases about octoprint-docker

[LongLiveCHIEF]

It looks like this ran when I was testing changes to workflows, and was not triggered via dispatch. Triggered from my own fork https://github.com/LongLiveCHIEF/octoprint-docker/actions/runs/363529242

[jwaes]

Having the same issue ... 'watchtower' upgraded my image to :latest, then i got a message inside octoprint to 'upgrade' ... which was a downgrade to 1.4.2 and that fscked up my install.

My octoprint running in docker no longer gets past the Connecting to OctoPrint's server... screen
from the logs:

octoprint.startup - INFO - Starting OctoPrint 1.4.2
all INFO log entries until
octoprint.server.util.flask.fix_webassets_filtertool - ERROR - Got an exception while trying to apply filter, ignoring file .... FileNotFoundError: [Errno 2] No such file or directory: '/usr/local/lib/python3.8/site-packages/octoprint/static/js/lib/jquery/jquery.ui.core.js'
When i go into the console of the container i actually see that there are jquery files, but not this one in that directory. I did remove the container and pulled it again but still the same issue. My /octoprint directory is mounted to a persistant volume

So the issue is that the jquery files are no longer there in the 'downgrade', as they moved to 1 js file ?

For temp fix i changed

image: octoprint/octoprint
to
image: octoprint/octoprint:1.4

in my docker-compose file.

[LongLiveCHIEF]

So the issue is that the jquery files are no longer there in the 'downgrade', as they moved to 1 js file ?

@jwaes this is most likely not a problem exclusive to docker, but I'll take a look.