You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been battling for a bit trying to understand why the pds service was crashing on startup on my server. After investigations, I found out that the root cause was that pds requires a CPU with sse4.2 which my server (old Atom) doesn't support.
For background, these are the symptoms:
the docker instance would start but pds would keep dying and restarting
It happens that sharp will use the system libvips by checking for the vips-cpp package using pkg-config. The simpler solution here, which would improve the portability and the security of the container would be to install vips-cpp on the image so when the install phase happens, sharp will use it. It does increase the time it takes to build the image because of the new packages to install and the time it takes to then build the C++ files that sharp uses. However, it's possible to only copy the libraries and reduce the actual impact on the image size.
I have it working locally and will send a PR soon.
I've been battling for a bit trying to understand why the pds service was crashing on startup on my server. After investigations, I found out that the root cause was that pds requires a CPU with sse4.2 which my server (old Atom) doesn't support.
For background, these are the symptoms:
/var/log/messages
After some research, it appears that
libvips
is used bysharp
which is directly included by atproto/pds (package.json).I would suggest to either:
lscpu
, ORThe text was updated successfully, but these errors were encountered: