-
Notifications
You must be signed in to change notification settings - Fork 28
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
Starting fresh (same Raspberry Pi, newer OS), sadly no results with 2.4.155. #109
Comments
Raspberry Pi 4B, right? Are you running Raspbian or something else? What's the OS (32 or 64bit?) / Docker version? Sounds like a permission issue, what command do you use to start / create the container? |
Went from Buster to Bullfrog, 64 bit Raspbian. The command used to create the container is the same one I've used that worked before, it is trying to startup, created all the folders and such. Docker 1.5-2, Docker-ce 5.19.03.15~30. The script I use to run it.
|
Bullfrog? I assume you mean Bullseye? |
Yes, sorry, Bullseye. I opened Synaptic to list the docker versions. Docker -v gives: Docker version 19.03.15, build 99e3ed8919. Docker was updated based on going to Bullseye from Buster, I saw it being updated. Docker containers I have for other things are working as expected. |
RangeError: Model is only valid from Tue Dec 10 2019 to Tue Dec 10 2024 I'll have to see if the version is newer than what I have (says latest), but that was over a week ago. |
Seems I updated at the wrong time! This time around it did come up, so I'm re-setting it up because it is well over a year old and the data there isn't worth anything. I didn't check, but is the expiration of the current one listed in the repo, if not, can you find it and add it? |
Seems to have been the same as #110 and works. |
First off, I moved the config that was there out, totally, so the config was a brand new folder with nothing in it.
I never got the intro to start setting it up, most likely due to the below, the log was non-stop spammed, why it fails.
/config/unms/logs/ucrm.log
This repeats:
The text was updated successfully, but these errors were encountered: