Comments on: Beginner’s Guide to Install and Use Docker with Raspberry PI

By: peppe8o

peppe8o — Mon, 02 Aug 2021 17:11:01 +0000

In reply to tarek soliman. Hi Tarek. Currently Odoo doesn't releases docker containers for ARM (you can check in OS/ARCH column from tag section in docker hub, https://hub.docker.com/_/odoo?tab=tags&page=1&ordering=last_updated). For this reason, if you want Odoo into a container you have to build it from scratch or from a ubuntu/debian base image

By: tarek soliman

tarek soliman — Sun, 01 Aug 2021 17:16:58 +0000

well, I am not able to get Odoo docker Image on Rasperrypi, with or without portainer. there is always errores. I wonder if Rancher can handle the issue. keep in mind that install Odoo on Ubuntu without Docker works fine. I hope you can help with new experiment to be able to install odoo docker image on rasberrypi Ubuntu or maybe Rancher. Thank you

By: peppe8o

peppe8o — Tue, 06 Apr 2021 21:23:55 +0000

In reply to Teodoro Visaires.

Hi Teodoro,
Plese copy an use the entire row from “docker run” to “linux-arm”

By: Teodoro Visaires

Teodoro Visaires — Tue, 06 Apr 2021 01:03:12 +0000

Hi,
After running this:
docker run -d -p 9000:9000 -v
I get this as response:
flag needs an argument: ‘v’ in -v

Any idea?

By: Sean S

Sean S — Sat, 27 Feb 2021 16:01:07 +0000

In reply to Ashley. Thanks, Ashley! This worked on my Pi3 Model B, too.

By: Robert

Robert — Sat, 19 Dec 2020 10:37:42 +0000

In reply to Robert.

Hi,
So I did it again (w/o uups), this time using the commands from the portainer site:
docker volume create portainer_data
docker run -d -p 8000:8000 -p 9000:9000 –name=portainer –restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce

and there was the exact same error message. However, I tried to run it nevertheless and it worked. So it might well be that it would have worked yesterday as well but I simply gave up after the error…

By: Robert

Robert — Sat, 19 Dec 2020 06:33:30 +0000

Hi,
Thanks for your efforts! This was all done for the first time so I guess the problem is on their end. However, since this is just a pet project (and there are locked up holidays ahead) I’ll wipe everything and start over again. Self education…
If I have any success I’ll let you know here!

By: peppe8o

peppe8o — Fri, 18 Dec 2020 20:27:39 +0000

In reply to Robert.

Hi Robert,
I used your command in my RPI3 and RPI4 and it works in my boards (standard RPI OS too). From what I’ve now checked in docker hub, I’m afraid that some confusion arised around the new “portainer-ce” container (with final “-ce” added): I can see that they still taggeg their image “linux-arm”, but OS/ARCH results amd64. So, if you previously pulled portainer-ce you could suffer this problem. Solution should be removing image (“docker image rm portainer/portainer-ce:linux-arm”) and then using their “portainer/portainer-ce:alpine” (but this evening I can’t download it, seems that there are problems on remote servers) or old image “portainer/portainer:linux-arm” (which works correctly for the moment).
As said,I’ve just tested old image (without “-ce”) and it currently works. As ce image will be available again, I will test this too.

By: Robert

Robert — Fri, 18 Dec 2020 18:27:43 +0000

Hi,
After running this:
docker run -d -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer:linux-arm
I get this as response:
$ The requested image’s platform (linux/amd64) does not match the detected host platform (linux/arm/v7)
I am currently running pi os 32bit. I have seen one similar message on github with some foggy replies. Am I the only one? Eveything is standard here, pi is 8GB (not that this matters)

rgds
rl

By: peppe8o

peppe8o — Wed, 16 Dec 2020 06:28:47 +0000

In reply to yshariff.

Hi yshariff,
I suppose you are writing about http://peppe8o.com/install-home-assistant-in-raspberry-pi-with-docker/ and your container stopped is the test one.
When you log-in again, you can restart your container with “docker start homeAssTest”. You can also check your stopped container with “docker ps -a”.
Consider that Test container (as defined in my post) is set to run as a test environment and only with terminal attached. To run it detached from terminal you have to add “-d” option on docker run command. To make it starting again after reboots you have to add the restart policy on docker run command (for example –restart unless-stopped).
Please refer to Production container references later on same post (http://peppe8o.com/install-home-assistant-in-raspberry-pi-with-docker/)