Skip to content
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

IOT stack vs raspberry pi OS bullseye #244

Open
pvklink opened this issue Nov 15, 2021 · 5 comments
Open

IOT stack vs raspberry pi OS bullseye #244

pvklink opened this issue Nov 15, 2021 · 5 comments

Comments

@pvklink
Copy link

pvklink commented Nov 15, 2021

I just installed Bullseye on my rpi, does IOTstack works on this latest OS ?

@Paraphraser
Copy link
Contributor

First, please see This project is dormant.

But, in answer to your question:

5D8E0EC1-A949-46B9-9D73-7FE94AC02BC5

I haven't tested every Docker container defined in IOTstack's templates but the signs are good. I do know that the "native install" of Home Assistant is broken but it's also broken for Buster. It's the result of the script the IOTstack menu uses (curl | sh) being broken.

@pvklink
Copy link
Author

pvklink commented Nov 17, 2021

He @Paraphraser
Yess docker is working on rpi bullseye by installing IOTstack

Some parts i dont get working like the docker api
Some of my containers (registry container) must be connectable from the LAN so that other rpi's can read my own docker hub thats in a container...

With previous docker installations i put this json file on /etc/docker/daemon.json so that the daemon also starts as a tcp service
But with current rpi bulleseye installation with IOTstack (fork) this does not work..
The api does not start with this extra json file, any tip ?
When i remove it, and reboot docker works.... but no lan accesss
`# place this file on /etc/docker/daemon.json so that i can connect to a docker fom the LAN

{
"debug": false,
"tls": false,
"hosts": ["tcp://0.0.0.0:2375", "unix:///var/run/docker.sock"],
"insecure-registries":["dockerhub:5000"]
}`

@pvklink
Copy link
Author

pvklink commented Nov 17, 2021

I do have a working solution to get the api working on tcp but dont now if this is decent workaround

sudo nano /usr/lib/systemd/system/docker.service
change ExecStart in ExecStart=/usr/sbin/dockerd -H unix:///var/run/docker.sock -H tcp://0.0.0.0:2375 --insecure-registry dockerhub:5000

sudo systemctl daemon-reload

The ideal situation is to have this file unchanged and use the json, but that did not work...

@Paraphraser
Copy link
Contributor

Way beyond my level of knowledge. Have you tried asking this question on Discord?

@pvklink
Copy link
Author

pvklink commented Nov 17, 2021

ok, i will.
You helped me a lot, i got docker working on bullseye, thank you very much!
and the above solution works !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants