Can't access <local IP>:2283 for setup after docker compose

Hey there, after getting docker to pull the correct images on my raspberry pi, I am now running into the issue where I can't access the server using the local IP and the port 2283, or at least nothing is happening when trying to. The port is opened on my router just like :22 and :80 are (I can access my website hosted via nginx for example). Did I miss something in the setup, do I need to open the port on the server as well? Thank you in advance!
31 Replies
Alex Tran
Alex Tran2y ago
Can you help posting the logs of Immich server?
Marvin Jérôme Stephan
all of the docker immich logs are empty
Alex Tran
Alex Tran2y ago
let's bring the containers down then run docker-compose up then see the logs
Marvin Jérôme Stephan
so just docker stop them? still empty after stopping and removing them
Alex Tran
Alex Tran2y ago
docker compose down would stop them then docker compose up would bring up the stack
Marvin Jérôme Stephan
still empty
Marvin Jérôme Stephan
this is my router config, so that shouldnt be the issue
No description
Alex Tran
Alex Tran2y ago
Can you please help me take a screnshot after the docker compose up command?
Alex Tran
Alex Tran2y ago
without the -d flag please so we can see the logs
Marvin Jérôme Stephan
Yeah thats... something
No description
Alex Tran
Alex Tran2y ago
oh my what is going on here
Marvin Jérôme Stephan
Further info about my kernel. should be arm64 aka aarch64 aka arm/v8, seems to all be the same thing. Don't know if that could be the issue since I needed to add "platform: linux/arm64" to all the services in the docker-compose.yml
No description
Alex Tran
Alex Tran2y ago
it might be the curlpit try without adding the platform clause and repull the images again
Marvin Jérôme Stephan
Then I get the error "no manifest for linux/arm/v8" as per https://discord.com/channels/979116623879368755/1112067844939714752/1112067844939714752 which is stupid, since technically arm/v8 and arm64/v8 should be the same thing
Alex Tran
Alex Tran2y ago
Are you running raspbianOs?
Alex Tran
Alex Tran2y ago
Can you run UbuntuOS instead? Use the Ubuntu Server 22.04.2 LTS 64-bit Image at https://ubuntu.com/download/raspberry-pi
Ubuntu
Install Ubuntu on a Raspberry Pi | Ubuntu
Ubuntu is an open-source operating system for cross-platform development, there's no better place to get started than with Ubuntu on a Raspberry Pi
Marvin Jérôme Stephan
Oh my. Have another few services running on this pi, is there any easy way to transfer?
Alex Tran
Alex Tran2y ago
depends on which services you have, can you list them?
Marvin Jérôme Stephan
Actually its just an nginx for my website and samba for easy file access, though I'd hate losing their configs wherever they may be
Alex Tran
Alex Tran2y ago
I can you can find those samba setting rather easily. How many website do you have that use nginx?
Marvin Jérôme Stephan
Just two, hah. though isn't ubuntu also substantially slower and less efficient on small systems compared to debian? Or ist htat just a rumor?
Alex Tran
Alex Tran2y ago
I would say it might be but negligible since you will be running the server image anyway, so it is lightweight Do you want to take a time to learn about Caddy proxy? 😉 gonna be 2 lines of config for your websites and you automatically get https
Marvin Jérôme Stephan
... and theres no way getting it running on debian?
Alex Tran
Alex Tran2y ago
I think the RaspianOS image might have something weird going on with these architecture thing :/
jrasm91
jrasm912y ago
Exit code 159 is illegal instruction btw. You are still not running the correct version of os/kernel + docker images (wrong platform)
Marvin Jérôme Stephan
Ughh. Probably like Alex said, might be that Raspian is reporting a weird architecture even though its just aarch64
jrasm91
jrasm912y ago
It is not a matter of reporting. Exit code 159 means it's actually running a wrong build
Marvin Jérôme Stephan
But what could be the culprit then? My pi is on aarch64

Did you find this page helpful?