-
-
Notifications
You must be signed in to change notification settings - Fork 124
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
Documentation: Docker installation and architecture #871
Projects
Comments
There hasn't been any activity on this issue recently. In an effort to provide a better overview of current issues we automatically clean some of the old ones. Many of them may already be resolved in newer versions of room-assistant. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is not a bug with the software. Instead it's a problem with the installation documentation found at https://www.room-assistant.io/guide/quickstart-docker.html
For the past 2 days I've been trying to get a Docker install of Room-Assistant running on my RPi3. Not thinking about the hardware differences between the RPi3 and my other 2 boxes I set Room-Assistant up on, I was encountering the following
error - ExceptionHandler: EAFNOSUPPORT, Address family not supported by protocol
Only while I was looking at the listing on Docker as I was writing up my report for an open issue did I realize that the Docker image I was pulling for this box should be different than the two AMD64 machines I'm running. (I rarely do anything on this machine as it's primarily meant to provide stability for my IoT hardware, so I forgot that it's not the normal machine hardware I use).
I'd like to suggest that the Docker documentation for a new install list the different architecture that can be pulled for a container. Currently the documentation only lists the Seeing a list for arm7 and aarch64 builds probably would have saved me a lot of time.
Thanks for all your time and effort on this project!
The text was updated successfully, but these errors were encountered: