-
Notifications
You must be signed in to change notification settings - Fork 10
Description
Hi! I just want to preface that I’m new to this process; however, I will try to outline the problems I’m encountering as to help give greater context.
I was able to clone your repo to my raspi, but I have been running into an issue where after I attempt to run
For stage in build-env server-deb desktop-deb; do
./build.sh buster “${stage}”
Done
I will get to a point where the process will start running and then, within ~ 5 minutes, it will force my raspi to restart (often with a message with the pid not being able to be found after the reboot)
After trying two separate memory cards (125 GB +) as well as swiping out my power supplies, I am still left with the same issue.
Alternatively, I attempted to work off of the dockerhub files in hopes that would lead to something. I was able to successfully, pull your docker files from the dockerhub (e.g. “docker pull arturklauser/raspberrypi-rstudio-build-env:1.2.5033-buster”) for all four steps that you outlined in your documents.
One thing that I recognized when trying to run (“./build.sh buster server”) was that the build shell script references a different version_patch than what is on the docker hub (1.2.5042 vs 1.2.5033 respectively). After changing that version_patch value in my build.sh script, I was able to complete the aforementioned command. Unfortunately, after running
docker run --rm --name rserver -v $PWD/work:/home/rstudio -p 8787:8787 -d arturklauser/raspberrypi-rstudio-server:1.2.5033
I was met with an ‘initialization error’; this came directly after trying to login at the http://<your_raspberry_pi>:8787 site with the default ‘rstudio’ username and ‘raspberry’ password.
I am unsure if my failure to build all parts sequentially would have led to the errors that I’m seeing; if so, do you have a suggestion on how to fix the automatic restart of my raspi?