Closed oliverhihn closed 2 years ago
Not completely sure but the deprecation warning might be coming from a dependency. I will have to check in detail.
Regarding your problem with the images not being properly processed: please check the permissions on your photos folder. I think photo-stream is unable to write the processed image files to the folder because it might be read-only.
It was read only. But even after fixing that and recreating the container, logs still give the same error message. I also noticed a warning whilest building:
Building photo-stream
Step 1/10 : ARG BASE_IMAGE=ruby:3.1.2-alpine3.15
Step 2/10 : FROM ${BASE_IMAGE}
---> 9eea51636263
Step 3/10 : ENV VIPSVER 8.12.2
---> [Warning] The requested image's platform (linux/arm/v6) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
---> Running in a881bc928671
Removing intermediate container a881bc928671
---> 7d7e1061419b
Step 4/10 : RUN apk update && apk upgrade && apk add --update --no-cache build-base glib-dev libexif-dev expat-dev tiff-dev jpeg-dev libgsf-dev git rsync lftp openssh && rm -rf /var/cache/apk/*
---> [Warning] The requested image's platform (linux/arm/v6) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
---> Running in c1ac92b90b97
But I don't think, that this is the problem. Or could it be the problem?
Sorry I didn't saw it earlier, but in #30 you said you're running this on a Raspberry Pi 4 Model B. While that should be backwards compatible with arm/v6 you really should be using arm64/v8 like the warning message tries to tell you. I would definitely switch over to that architecture and by doing so you could actually just use the image I provide on Docker Hub.
Not sure if this will fix everything on your end but please do so and report back.
As far as i understand, I am using linux/arm64/v8
(as it says in the warning detected host platform (linux/arm64/v8)
) and the image platform is (linux/arm/v6)
. So I should downgrade from v8 to v6 now?
I can confirm that im using v8:
root@pi:$ uname -r
5.15.32-v8+
What it says is you requested a v6 image while your host (your pi) is v8. As far as I can tell you followed the instructions in the README regarding Raspberry Pi but that is actually for v6 only. I probably should highlight that.
So basically just revert your changes in the docker-compose.yml and build the image again or use the pre-built image I provide on Docker Hub by pulling it:
docker pull waschinski/photo-stream:latest
which you can then run by e.g.
docker run -i -t waschinski/photo-stream /bin/bash
Okay i tried that. Same error. Then I did a docker system purge -a
to make sure all images and build cache is cleaned. Then i deleted the cloned repo, and cloned a fresh copy. Then I modified the permissions of photos/ and original/ and all .jpg files inside original. Still the same (Errno::ENOENT) logs. At this point I dont know what I could possibly be doing wrong.
But when I do docker run -p 80:80 -i -t waschinski/photo-stream /bin/bash
I get the "No photos!" Page. So I tried to delete all the photos from photos/original and ran docker-compose up
it worked without errors! I also get the error page saying that there are no photos. So to me it seems as if there is just a problem converting photos from original dir. But why?
Update: I found an error in the volume key of the docker-compse.yml and fixed it. Made an PR where I explain it.
After the change in the docker-compose.yml it now successfully build. Thank you again for the fast help, but now it still doesn't work on my Raspberry Pi. I tried it with the example pictures and also with a own picture in jpg format. Bouth give the same error. Am I missing something or doing something wrong? Also I would love to help solving that
deprecated
call warning but I cannot find the file where this is called.Output of
docker logs photo-stream