Error installing on Synology NAS: "failed to get urandom" #1239
Comments
|
Looks like this might be a bug in Ruby or bundler. I'll update the versions and you can try the |
|
This seems to be a Synology specific error. Setting up the app using the |
|
#1247 may help. It should be in tonight's nightly image, so maybe see if that helps. |
|
@mvkalsbeek did the nightly image help at all? |
Not at the time of that post. It works fine on a Windows machine, doesn't seem to work on Synology. The nightly gave the same error log as the 0.44 image. Will try the latest nightly asap! |
|
I just realised I broke |
|
FWIW I have 0.47.1 running on Synology DSM 7.2 via a Docker container. I had to run (also, hi James!) |
|
ANDY! Yay :) Thanks for that, good to know it works and about the ghcr problem... one for the docs. |
|
I'll do a quick post about it somewhere and let you know. |
|
I've got some brief instructions on how I got up-and-running on Synology here. |
|
There's more detail on successful setup in #1471 which should roll into any documentation. |
|
Took some time to retry installing VanDAM/Manyfold on a Synology NAS. I've tried the 0.54.2 image but it still seems to crash on getting some required ruby gems, this time the |
|
Interesting, error is |
|
@mvkalsbeek could you try the test in this comment on your NAS, see if it throws the same error? pglombardo/PasswordPusher#647 (reply in thread) |
|
@mvkalsbeek I've opened a separate issue for this: #1766 |
|
Sorry, it didn't need a new issue, it's the same as your original report. Ignore me. |
Floppy
changed the title
|
I came across @mariushosting's instructions for Synology (now linked from the website), and he confirms that the urandom problem is an issue with Synology kernels below version 4. @mvkalsbeek I guess yours is running version 3? From his troubleshooting guide at https://mariushosting.com/synology-common-docker-issues-and-fixes, I'm not sure there's anything we can do... you were originally installing v0.44.0 when you hit the problem, which didn't have the I'm closing it on the assumption you're on a too-old kernel, but if you're on v4 and it looks like it should work, feel free to reopen. |
|
Looking around, the same issue has cropped up on nextcloud, xibo, postal and no doubt many others. It looks like it might be possible to build your own docker image based on a different base distribution; some nextcloud people used buster, and there is a Ruby |
|
Actually, the nextcloud thread implies that Line 1 in c40cc05 FROM ruby:3.2-bullseye AS build, build the image, and see if it works!
(I'm assuming some experience with building docker images here, apologies if that's not helpful) |
|
If you try and it does work, then I could set up a docker build to create a bullseye-based image automatically, at least until they stop supporting it with new Ruby base images. |
Can you make it as i have the same issue and no knowledge to do it :D |
|
Your NAS Have and old kernel 3x Kernel. Just buy a new NAS. |
if i had the funds to do it i would |
I have pulled the latest (0.44.0) docker image with the
docker pull ghcr.io/floppy/van_dam:latestcommand on a Synology NAS from the CLI and created a container using the Docker GUI. Trying to start the container however is unsuccessful and generates the following error log:Is this a Synology specific error, or am I missing some configuration, environment variables or dependencies?
The text was updated successfully, but these errors were encountered: