Octobot hosted on RPI no longer working (Executable + Docker)

[WilcoSnel]

Step 1: Have you search for this issue before posting it? Yes

If you have discovered a bug in the bot, please search our issue tracker.
If it hasn't been reported, please create a new issue.

Step 2: Describe your environment

• OS : Raspberry Pi OS (Lite) 64-bit
• Python Version: 3.11.2

Step 3: Describe the problem:

Describe the bug
I was using the executable version of 2.0.5 on Raspberry Pi OS 64-bit on a Rpi 3B+. After 2.0.6 was released the update button appeared. I clicked it and after a couple hours nothing seemed to have happened. I retried a couple times, but no dice. Restarted the Pi and tried again. No change. After that I decided to update Raspberry Pi OS using sudo apt update > sudo apt full-upgrade. After that Octobot stopped working all together. So tried a fresh install of Raspberry Pi OS. And after that didn't work the Lite version (no GUI) icw Docker. But this does not work either. I just can't seem to get the web server running again with 2.0.6.

Expected behavior
Update without issue or at least get it working on a fresh install with 2.0.6.

Steps to reproduce:

1. Fresh install of RPI OS 64 bit Lite
2. Follow Docker installation instructions

Observed Results:

• What happened? Octobot does not become available on IPaddress:5001
• What did you expect to happen? Octobot to become available on IPaddress:5001

Relevant code exceptions or logs:

If applicable, add screenshots to help explain your problem.

// paste your log here

[DrBlackross]

just goto the ip of the RPI in your browser (minus the port), its what i did, i expected the same thing lol... or check and see if port 5001 is forward in docker to port 80, if not just change it and just rebuild the image without pulling it (uncheck the "Always pull the image" option).

[WilcoSnel]

just goto the ip of the RPI in your browser (minus the port), its what i did, i expected the same thing lol... or check and see if port 5001 is forward in docker to port 80, if not just change it and just rebuild the image without pulling it (uncheck the "Always pull the image" option).

If that's the case the instructions should be updated. I actually got it running again using the raspberry pi instruction. It seems the CLI/Non-GUI/Lite version of the OS is just not working however. The full OS is needed. As the Gui can be a drain on resources, it might be nice to make Octobot compatible with the Lite version of the OS. That's the real question here.

[DrBlackross]

hmmm, is docker pulling the right architecture? i run mine on a rpi 3+ but i used to have to make sure it was pulling aarch64

docker gives me no issues on the PI, but, i do run my PI headless and use the octobot website access in a local browser from another computer on my local network.

Linux DayTrader 6.6.51+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.51-1+rpt3 (2024-10-08) aarch64

DayTrader:~ $ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
drakkarsoftware/octobot stable 53b822e5e332 3 weeks ago 709MB
portainer/portainer-ce 2.21.3 5c31d4a1c6e9 3 weeks ago 293MB

and my docker ports are default (via portainer webpage install)

Port configuration
0.0.0.0:80 -> 5001/tcp
:::80 -> 5001/tcp

(note: i have not updated to the 2.0.7 version yet.)

but for having upgrade hassles in the past, i keep my directories separate and not in docker volumes /\ makes it easier to edit the tentacles with the " 4h" issues i have with coinbase exchange when back-testing as well as not having enough data to start trading immediately and waiting a day or two for it to spool up enough data to start.

also, most of the tentacles look for " 4h" data plots coinbase uses " 6h" candle time mark (just hit the drop down on any exchange on their charts and it should list all the candle times if you or anyone has issues with back-testing)

(just an extra heads up)