45 Replies
linux/arm/v8 = 32 bit os. You should be pulling
linux/arm64/v6 = 64 bit os.
How?
I changed it as whichever one I try and pull I get the same error
You probably need to re-install an operating system on your PI with a 64 bit kernal.
O
Hang on
Aarch64
I did change it
A while ago
There is a config file that changes that
As it set 64bit from 0 to 1 to be able to run photoprism
What is the output of
lscpu?And that worked first time
Here
I wonder if you need to re-install docker after changing it to 64 bit?
Photoprism worked fine
Immediately
It uses docker?
Yes
Running healthy ever since I changed to 64bit
Well, for some reason it thinks you have a 32 bit os and it requesting that version of the docker image. You can override that and specify a specific architecture though
Got it how
In my yml file
I believe you can just add something like:
It's really weird photoprism pull the 64bit version on its own
To each service, under
image: ... or so.O thx I will try
Under image didn't work
@RefinedTheMite
try this docker-compose
so
sudo docker compose up -d
(plz ping me if it works :happ: )It kind of works @Onelots. but it keeps on restarting
Like every couple of seconds
Any ideas much appreciated
:Think:
Try to deploy using docker compose
Stack system isn't really good I think
The way you deploy it with web editor
You should look at the exit code. It might have pulled and started, but if you are running it on the wrong architecture it could throw an illegal instruction, which causes it to crash loop.
I did, I just use portainer to get visual look at all of my containers
There are no logs and also portainer can't seem to give me an exit code since it stops for like a few milliseconds then restarts so all portainer states that it is healthy but has restarted more than 29 times.
You'd have to run
docker ps -a to see the exit code.Ok
Nope
Just restarting
That's what is says
Also weird that there are no logs
At all
Maybe update the compose file to not have "restart: always" and redeploy
Errr ok
Now I have done that it is giving me an exit code 159
@Onelots.
159 is illegal instruction.
The docker image isn't completed for your kernal/os and docker was probably right asking for Linux/arm/v8 to begin with.
Right...
Any fix...
I mean, I'm no expert but it looks like you aren't actually running a 64bit install of something.
Errr
Either docker, kernal, os, etc.
Hummm
Os is cpu is docker might not be
Just to leave it if anyone knows how to fix that will be great error 159 using
This
I'll try an other fix tonight
I'm not home currently
Dw I have moved to photoprism as that works
...