Incorrect display of images in the plank service #395

Closed
opened 2026-02-04 19:00:20 +03:00 by OVERLORD · 12 comments
Owner

Originally created by @SterhLight on GitHub (Dec 29, 2023).

I encountered a problem in which, after installing the service using docker-compose, the images (screenshots in the attachment. as it is in the plank and the original) are displayed incorrectly in the bar. What could it be? How to fix it?
52
53

Originally created by @SterhLight on GitHub (Dec 29, 2023). I encountered a problem in which, after installing the service using docker-compose, the images (screenshots in the attachment. as it is in the plank and the original) are displayed incorrectly in the bar. What could it be? How to fix it? ![52](https://github.com/plankanban/planka/assets/122260062/2a235c5f-7404-40d4-b06a-c59ad71aecc9) ![53](https://github.com/plankanban/planka/assets/122260062/e218f57c-8335-4b7a-96bb-0e844f5b9476)
Author
Owner

@idle-mind commented on GitHub (Jan 2, 2024):

Also seeing this with some Jpeg images running latest docker image.
thumbnail looks likes it's black and white when opened directly from disk so not an issue with browser display.

@idle-mind commented on GitHub (Jan 2, 2024): Also seeing this with some Jpeg images running latest docker image. thumbnail looks likes it's black and white when opened directly from disk so not an issue with browser display.
Author
Owner

@idle-mind commented on GitHub (Jan 3, 2024):

Here is an issue in sharp that looks like it related to our current black and white images.
https://github.com/lovell/sharp/issues/3893#issuecomment-1851490893

@idle-mind commented on GitHub (Jan 3, 2024): Here is an issue in sharp that looks like it related to our current black and white images. https://github.com/lovell/sharp/issues/3893#issuecomment-1851490893
Author
Owner

@idle-mind commented on GitHub (Jan 3, 2024):

For testing purposes i ran npm update sharp in my docker container to pickup the newer release.
After restarting the container the image attachment is working now.
So possibly just need to bump the sharp lib version, but not sure what else may be needed.

@idle-mind commented on GitHub (Jan 3, 2024): For testing purposes i ran npm update sharp in my docker container to pickup the newer release. After restarting the container the image attachment is working now. So possibly just need to bump the sharp lib version, but not sure what else may be needed.
Author
Owner

@SterhLight commented on GitHub (Jan 3, 2024):

Yes, I'm just using Proxmox
if you mean this:
docker exec -it /bin/bash
npm update sharp
exit
docker restart container

then in my case it didn't work.

@SterhLight commented on GitHub (Jan 3, 2024): Yes, I'm just using Proxmox if you mean this: docker exec -it <container> /bin/bash npm update sharp exit docker restart container then in my case it didn't work.
Author
Owner

@meltyshev commented on GitHub (Jan 3, 2024):

Thanks for reporting this! I'm gonna try fixing it now. I apologize for the late replies, still on vacation 😀

UPD: Could someone please provide an image that is not displaying correctly after uploading? I haven't been able to reproduce it yet... I've realized that it would be difficult to reproduce without virtualization. Thinking...

@meltyshev commented on GitHub (Jan 3, 2024): Thanks for reporting this! I'm gonna try fixing it now. I apologize for the late replies, still on vacation 😀 UPD: ~~Could someone please provide an image that is not displaying correctly after uploading? I haven't been able to reproduce it yet...~~ I've realized that it would be difficult to reproduce without virtualization. Thinking...
Author
Owner

@meltyshev commented on GitHub (Jan 3, 2024):

I've updated sharp in the dev image.

Please try to change the image in docker-compose.yml from ghcr.io/plankanban/planka:latest to ghcr.io/plankanban/planka:master and check images there.
If this won't work, try adding VIPS_NOVECTOR=0 environment variable to docker-compose.yml and restart the container.

Please let me know if any of this works, then I'll make a release.
And also don't forget to change the image back, it's better not to use dev image in production.

@meltyshev commented on GitHub (Jan 3, 2024): I've updated sharp in the dev image. Please try to change the image in `docker-compose.yml` from `ghcr.io/plankanban/planka:latest` to `ghcr.io/plankanban/planka:master` and check images there. If this won't work, try adding `VIPS_NOVECTOR=0` environment variable to `docker-compose.yml` and restart the container. Please let me know if any of this works, then I'll make a release. And also don't forget to change the image back, it's better not to use dev image in production.
Author
Owner

@SterhLight commented on GitHub (Jan 4, 2024):

I've updated sharp in the dev image.

Please try to change the image in docker-compose.yml from ghcr.io/plankanban/planka:latest to ghcr.io/plankanban/planka:master and check images there.

Hello. None of what was proposed gave the expected result. The pictures are still negative. Please note that this only applies to images inside the plates.

55

@SterhLight commented on GitHub (Jan 4, 2024): > I've updated sharp in the dev image. > > Please try to change the image in `docker-compose.yml` from `ghcr.io/plankanban/planka:latest` to `ghcr.io/plankanban/planka:master` and check images there. > Hello. None of what was proposed gave the expected result. The pictures are still negative. Please note that this only applies to images inside the plates. ![55](https://github.com/plankanban/planka/assets/122260062/db4c7f38-8726-4e94-9444-69bbbf31dc11)
Author
Owner

@idle-mind commented on GitHub (Jan 5, 2024):

Can confirm that moving to master tag did not resolve & black/white returned.
After return to latest tag and running npm update sharp & container restart it is working again.

Let me know if you need any more info or testing help.

@idle-mind commented on GitHub (Jan 5, 2024): Can confirm that moving to master tag did not resolve & black/white returned. After return to latest tag and running npm update sharp & container restart it is working again. Let me know if you need any more info or testing help.
Author
Owner

@SterhLight commented on GitHub (Jan 5, 2024):

npm update sharp
exit
docker restart container

Why didn’t these "npm update sharp" and "docker restart container" commands work for me? :(

@SterhLight commented on GitHub (Jan 5, 2024): > npm update sharp > exit > docker restart container Why didn’t these "npm update sharp" and "docker restart container" commands work for me? :(
Author
Owner

@meltyshev commented on GitHub (Jan 7, 2024):

This is very strange, as we also use Proxmox, but we don't have this problem and can't even reproduce it...

I also found one of the solutions here: https://github.com/lovell/sharp/issues/3893#issuecomment-1877002141, it might solve the problem for a while until an update comes out with a fix.

Setting the CPU Type in Proxmox to "Host" instead of "default" did indeed solve the issue for me.
Thank you very much for the hint!

@meltyshev commented on GitHub (Jan 7, 2024): This is very strange, as we also use Proxmox, but we don't have this problem and can't even reproduce it... I also found one of the solutions here: https://github.com/lovell/sharp/issues/3893#issuecomment-1877002141, it might solve the problem for a while until an update comes out with a fix. > Setting the CPU Type in Proxmox to "Host" instead of "default" did indeed solve the issue for me. > Thank you very much for the hint!
Author
Owner

@daniel-hiller commented on GitHub (Jan 7, 2024):

Hi,
i was able to reproduce the problem on my homeserver .
I'm using Proxmox 8.1.3 with an i5 11600T

To fix the problem....

Click on the VM > Hardware > edit Processors > set Type to host
Restart your VM and everything should be ok

Like this
image

@daniel-hiller commented on GitHub (Jan 7, 2024): Hi, i was able to reproduce the problem on my homeserver . I'm using Proxmox 8.1.3 with an i5 11600T To fix the problem.... Click on the VM > Hardware > edit Processors > set Type to host Restart your VM and everything should be ok Like this ![image](https://github.com/plankanban/planka/assets/46579393/49ab9a9c-5a0b-439e-9b17-3cd8c547d794)
Author
Owner

@SterhLight commented on GitHub (Jan 9, 2024):

Hi, i was able to reproduce the problem on my homeserver . I'm using Proxmox 8.1.3 with an i5 11600T

To fix the problem....

Click on the VM > Hardware > edit Processors > set Type to host Restart your VM and everything should be ok

Yes. That helped. Thank you.

@SterhLight commented on GitHub (Jan 9, 2024): > Hi, i was able to reproduce the problem on my homeserver . I'm using Proxmox 8.1.3 with an i5 11600T > > To fix the problem.... > > Click on the VM > Hardware > edit Processors > set Type to host Restart your VM and everything should be ok Yes. That helped. Thank you.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#395