Closed kallqvist closed 5 years ago
Just an update here: Today I randomly downgraded to stevearc/pypicloud:1.0.2 and it works just like before.
Not sure if that is the newest released version I would be able to run but somewhere between that label in docker hub and "latest" something did break
Ah, I see what's going on
https://github.com/stevearc/pypicloud-docker/commit/78898ecb85ace31b75e09391db4f5f25f623188e and https://github.com/stevearc/pypicloud/commit/fec2d1c3f779f375a1b2fed14d5bef2d45984eb0#diff-85e379d391894a5ea8fe9c70abdfb933 changed the configuration so that the virtualenv at /env
no longer exists. If you remove the virtualenv
line from your config file it will likely work. It may be best to regenerate the config file from the tool and re-apply your changes on top, just to be sure.
Sorry about the trouble!
Ah, yes it worked! No worries and thanks for a great release btw! Best "it just works"-solution for self-hosted pypi I've seen. :)
A python import error have started to appear on every boot of containers from this image. AFAIK nothing in my environment have changed (except probably the version of this image).
I was foolishly running this from the latest-tag and not upgrading for a long while until a couple of weeks ago so I don't really know what version I've been successfully running before...
I've tried a couple of older versions of docker image but with the same result for all of them. Any ideas?
Thanks!