Closed lbesnard closed 1 year ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
I'd like to add that even using the previous image nextcloud:27.0.1-ls258
leads to the same problem with hexhamming
@lbesnard It looks like hexhamming was last released a year and a half ago, which was before the python 3.11 releases. Therefore pypi does not contain the wheels for 3.11, which nextcloud got rebased on recently.
I just pushed the wheels to our own repo so it should work now. I also have an update for the mod to fix some of the optional dependencies.
If you can test this PR mod and let us know if it works, it would be much appreciated:
ghcr.io/linuxserver/mods:pull_request_733
You would replace linuxserver/mods:nextcloud-mediadc
with ghcr.io/linuxserver/mods:pull_request_733
in the DOCKER_MODS
variable to test.
Thanks
PR for reference: https://github.com/linuxserver/docker-mods/pull/733
Perfect! Thanks a lot for such a quick fix. My instance works as expected.
Cheers
Is there an existing issue for this?
Current Behavior
I've never had major issues with my nextcloud instance from linuxserver over the years, but this error got me stuck. I'm not quite sure what triggered the issue, as the last nextcloud update I performed was a few weeks ago and worked fine. Also I have watchtower running in this container, so an image from the last few weeks could have been the cause of the issue.
When starting, I noticed this message:
But I believe the issue is not about the ownership but about corrupted files created during the previous
up -d
of the container while trying to install the hexhamming python package.I tried running a new container, with my existing
/data
folder, but a new empty/config
folder, however the initialisation of the container always fail because of hexhamming regardless of using the old or new config folder:I found that this issue had somewhat similar logs,https://github.com/linuxserver/docker-nextcloud/issues/312, but I believe this must be different.
Anyway I'm pretty stuck
Expected Behavior
I can spin my nextcloud instance fine
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs