-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
baikal docker for synology diskstation #69
Comments
I'll try to add an image for the |
Hi @nillebor , the version 0.9.1 images should now support the i386 platform - can you give them a try and see if your error goes away? |
thx i will test it! I'll see tomorrow or the day after once again |
For now you can use any of the experimental tags (https://hub.docker.com/r/ckulka/baikal/tags?page=1&name=experimental), e.g.
Once I know they are working I release them und |
hello kulka I want to give a brief info - Baikal Docker on the Diskstation works fine. thanks for that. i only have one x86/i386 diskstation, so I can't say anything about a modern x64 diskstation. I tested the following versions:
if I saw this correctly, is php8.1 installed in the Apache & nginx version? I'm sticking with nginx with php_8.1. Can you also offer a "latest version" for nginx that makes it easier to update? Do you have any information about what the error can be with apache?does the error message tell you anything? Please continue and maybe they will make a "latest" Nginx version ;) many thx |
Thanks for the update! Glad Nginx is working out.
I was looking around more, looks like quite a lot of people have the AH00141 error with Synology, e.g. https://github.com/bitnami/bitnami-docker-apache/issues/106 and nextcloud/docker#1574. From what I'm reading, it's due to the kernel version that's missing components required by Apache. You'd normally fix this by updating the kernel, but apparently no updates are available by Synology. One of the issues mention an escape hatch: build the Apache image with an older base image, which I could release as it's own variant, similar to what I did with the PHP 8.0 and 8.1 image variants. It'll make things slightly more confusing because of the inflation of image variants, but it could be a way out. But since Nginx seems to work: unless Nginx isn't viable for other reasons and Apache is a must, I'd like to keep things simple as they are now and stick to the latest versions... let me know what you think. On a sidenote, there's also https://stackoverflow.com/questions/17884176/apache-could-not-initialize-random-number-generator that says illegal characters in the
Yes, the
Can you elaborate? Not sure if I understand correctly, do you mean that the Nginx image should be |
thank you for your great work. The errors with Apache and Synology should not be a problem, because I can live with it well. Also php_8.1 works without problems on last DSM7.0 (1513+/i386) - I love it - I'm really happy with it! Edit: Please keep it up. cheers |
Ah, I see what you mean and the good news is that it's already set up that way: the I didn't prefix it with What is troubling is that Can you please run |
the tag nginx to always get the latest version is completely sufficient, name adjustment is still not necessary. everything can remain as it is. my problems are completely solved the contribution can be closed. Iam very, very very happy |
Thank you, appreciate the feedback, it's always nice to hear :) |
i have been using the baikal server for many years.
i use this on a diskstation with intel processor.
unfortunately, your docler package does not work, you receive the error message "Function not implemented: AH00141: Could not initialize random number generator"
could it be because the i386 (x86) is currently not supported?
could you offer the support, because I use several dockerfiles and the administration would be easier.
The text was updated successfully, but these errors were encountered: