2008-01-16, 00:24
I would like to request BOINC as a feature.
(2017-01-15, 05:12)aptalca Wrote: Just throwing it out there, I have a docker image in my personal repo for BOINC.
If you're using LE on x86, this would work.
It is running the server and the client, and you can access the gui in a browser window from another computer (through some xrdp magic).
A few downsides:
1) X86 only (no arm or aarch64 build)
2) CPU only (never tried gpu assist, may or may not work)
3) Image is fairly large (due to the gui and all)
Upside is, it works and it is fairly easy to install.
On LE, install the docker service addon from the LE repo. After that, you can install this through command line (ssh would also work)
Here's the docker image: https://hub.docker.com/r/aptalca/docker-rdp-boinc/
docker pull aptalca/docker-rdp-boinc
docker run -d --name="RDP-Boinc" -e HEIGHT="720" -e WIDTH="1280" -v /storage/boinc:/config:rw -e TZ="Europe/Podgorica" -p 8083:8080 aptalca/docker-rdp-boinc
nano /storage/.config/autostart.sh
(
docker start RDP-Boinc
) &
docker stop RDP-Boinc
docker rm RDP-Boinc
docker run -d --name="RDP-Boinc" -e HEIGHT="720" -e WIDTH="1280" -v /storage/boinc:/config:rw -e TZ="Europe/Podgorica" -p 8083:8080 aptalca/docker-rdp-boinc
docker rm RDP-Boinc
docker run -d --name="RDP-Boinc" -e HEIGHT="720" -e WIDTH="1280" -v /storage/boinc:/config:rw -e TZ="Europe/Podgorica" -p 8083:8080 aptalca/docker-rdp-boinc
(2017-01-15, 21:51)mladen.perisic Wrote:My guess is that when you reboot, the container is not stopped cleanly and that's why it has issues afterwards.(2017-01-15, 05:12)aptalca Wrote: Just throwing it out there, I have a docker image in my personal repo for BOINC.
If you're using LE on x86, this would work.
It is running the server and the client, and you can access the gui in a browser window from another computer (through some xrdp magic).
A few downsides:
1) X86 only (no arm or aarch64 build)
2) CPU only (never tried gpu assist, may or may not work)
3) Image is fairly large (due to the gui and all)
Upside is, it works and it is fairly easy to install.
On LE, install the docker service addon from the LE repo. After that, you can install this through command line (ssh would also work)
Here's the docker image: https://hub.docker.com/r/aptalca/docker-rdp-boinc/
Following your guide on https://hub.docker.com/r/aptalca/docker-rdp-boinc/ I managed to run BOINC and now I'm crunching data! Thank you!
Here's what I did over SSH:
Just like you suggested I needed to replace original timezone command with my time zone.Code:docker pull aptalca/docker-rdp-boinc
docker run -d --name="RDP-Boinc" -e HEIGHT="720" -e WIDTH="1280" -v /storage/boinc:/config:rw -e TZ="Europe/Podgorica" -p 8083:8080 aptalca/docker-rdp-boinc
After that I created/edited autostart.sh inand put this in file:Code:nano /storage/.config/autostart.sh
so RDP-Boinc would be automatically started every time computer is turned on.Code:(
docker start RDP-Boinc
) &
I can check progress via Chromium plugin by visiting http://localhost:8083/#/client/c/Boinc from that computer or by IP address from other computers in network.
Your solution is quick, easy and more importantly - it works as intended! But after couple of manual computer reboots I noticed that something went wrong. By checking CPU and RAM usage I could see that BOINC is going thru data. When I try accessing xrdp over web I can see that Guacamole web server is up and running and I'm getting xrdp login window, but when I click Ok, xrdp is showing message that it could not connect. So, I'm guessing problem wasn't Guacamole or xrdp, but maybe xrdp access to BOINC manager? What do you think? Only quick'n'dirty solution I could think of was to remove RDP-Boinc docker and run it again (data and current progress were not affected):Code:docker stop RDP-Boinc
docker rm RDP-Boinc
docker run -d --name="RDP-Boinc" -e HEIGHT="720" -e WIDTH="1280" -v /storage/boinc:/config:rw -e TZ="Europe/Podgorica" -p 8083:8080 aptalca/docker-rdp-boinc
Maybe I should put in autostart.sh commands for removal and runing docker every time i turn on computer?Would this be right approach? I'm not familiar with dockers, so I'm not sure if this approach would make some strange gibberish on my storage?Code:docker rm RDP-Boinc
docker run -d --name="RDP-Boinc" -e HEIGHT="720" -e WIDTH="1280" -v /storage/boinc:/config:rw -e TZ="Europe/Podgorica" -p 8083:8080 aptalca/docker-rdp-boinc
(2017-01-16, 00:19)aptalca Wrote:Yes, I understand that. I thought docker system is designed that way. You are probably right - I noticed prolonged shutdown when docker is active which could indicate OS is waiting for app to close and then kill it. I will investigate later this week and report findings here. Thanks for the tip!(2017-01-15, 21:51)mladen.perisic Wrote:My guess is that when you reboot, the container is not stopped cleanly and that's why it has issues afterwards.(2017-01-15, 05:12)aptalca Wrote: Just throwing it out there, I have a docker image in my personal repo for BOINC.
If you're using LE on x86, this would work.
It is running the server and the client, and you can access the gui in a browser window from another computer (through some xrdp magic).
A few downsides:
1) X86 only (no arm or aarch64 build)
2) CPU only (never tried gpu assist, may or may not work)
3) Image is fairly large (due to the gui and all)
Upside is, it works and it is fairly easy to install.
On LE, install the docker service addon from the LE repo. After that, you can install this through command line (ssh would also work)
Here's the docker image: https://hub.docker.com/r/aptalca/docker-rdp-boinc/
Following your guide on https://hub.docker.com/r/aptalca/docker-rdp-boinc/ I managed to run BOINC and now I'm crunching data! Thank you!
Here's what I did over SSH:
Just like you suggested I needed to replace original timezone command with my time zone.Code:docker pull aptalca/docker-rdp-boinc
docker run -d --name="RDP-Boinc" -e HEIGHT="720" -e WIDTH="1280" -v /storage/boinc:/config:rw -e TZ="Europe/Podgorica" -p 8083:8080 aptalca/docker-rdp-boinc
After that I created/edited autostart.sh inand put this in file:Code:nano /storage/.config/autostart.sh
so RDP-Boinc would be automatically started every time computer is turned on.Code:(
docker start RDP-Boinc
) &
I can check progress via Chromium plugin by visiting http://localhost:8083/#/client/c/Boinc from that computer or by IP address from other computers in network.
Your solution is quick, easy and more importantly - it works as intended! But after couple of manual computer reboots I noticed that something went wrong. By checking CPU and RAM usage I could see that BOINC is going thru data. When I try accessing xrdp over web I can see that Guacamole web server is up and running and I'm getting xrdp login window, but when I click Ok, xrdp is showing message that it could not connect. So, I'm guessing problem wasn't Guacamole or xrdp, but maybe xrdp access to BOINC manager? What do you think? Only quick'n'dirty solution I could think of was to remove RDP-Boinc docker and run it again (data and current progress were not affected):Code:docker stop RDP-Boinc
docker rm RDP-Boinc
docker run -d --name="RDP-Boinc" -e HEIGHT="720" -e WIDTH="1280" -v /storage/boinc:/config:rw -e TZ="Europe/Podgorica" -p 8083:8080 aptalca/docker-rdp-boinc
Maybe I should put in autostart.sh commands for removal and runing docker every time i turn on computer?Would this be right approach? I'm not familiar with dockers, so I'm not sure if this approach would make some strange gibberish on my storage?Code:docker rm RDP-Boinc
docker run -d --name="RDP-Boinc" -e HEIGHT="720" -e WIDTH="1280" -v /storage/boinc:/config:rw -e TZ="Europe/Podgorica" -p 8083:8080 aptalca/docker-rdp-boinc
If recreating the container is working fine, then what you came up with is probably fine. Docker containers are designed to be temporary and easily deployable anyway. But there is always a chance that the data in the mapped config folder may get corrupted during an unclean shutdown.
The proper solution would be to create a service file (systemd) that starts and stops the container during system start and shutdown (or reboot). If you search on the libreelec forums, you should be able to find some samples for docker containers