It could be possible, because the image should also got updates for the underlying OS.
However, I tested this new image for ARM64 and it didn’t have this issue.
This is usually happen, if a ca-certificates package is not updated.
The OS is updated by the way: Dockerfile: upgrade distro buster to bookworm (#22) · storj/storagenode-docker@7784e2a · GitHub
And the actual problem in the linked thread is:
thus a solution:
Seems the docker engine may be changed?