if you are referring to https://github.com/LemmyNet/lemmy/blob/0.18.0-rc.4/Cargo.toml#L140 then it most likely has something to do with lemmy having its own embedded pict-rs, which is at version 0.4.0; whereas the ansible-playbook is still using an external pict-rs 0.3.1, maybe due to some issues with the 0.3 to 0.4 migration
to check if lemmy is using its embedded pict-rs, I think you can see if lemmy was started with the –features embed-pictrs command line option
Oh… that’ll probably be in the docker container log. I’m not sure if I can dig back that far… probably not :(
Yep aarrrrrghhhh it’s at when the container is initialized. Too late T_T
Maybe I can tell if I manage to start a separate instance, but I’m not sure if there’s enough hardware resources on my side to try. But I’ll open the ticket first regardless based on Crabby’s findings
if you are referring to https://github.com/LemmyNet/lemmy/blob/0.18.0-rc.4/Cargo.toml#L140 then it most likely has something to do with lemmy having its own embedded pict-rs, which is at version 0.4.0; whereas the ansible-playbook is still using an external pict-rs 0.3.1, maybe due to some issues with the 0.3 to 0.4 migration
to check if lemmy is using its embedded pict-rs, I think you can see if lemmy was started with the –features embed-pictrs command line option
Oh… that’ll probably be in the docker container log. I’m not sure if I can dig back that far… probably not :(
Yep aarrrrrghhhh it’s at when the container is initialized. Too late T_T Maybe I can tell if I manage to start a separate instance, but I’m not sure if there’s enough hardware resources on my side to try. But I’ll open the ticket first regardless based on Crabby’s findings