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

missing instructions for running the docker image at macOS #237

Closed
R0dri opened this issue Apr 6, 2020 · 6 comments
Closed

missing instructions for running the docker image at macOS #237

R0dri opened this issue Apr 6, 2020 · 6 comments
Labels
side topic How to use this and workarounds wontfix This will not be worked on

Comments

@R0dri
Copy link

R0dri commented Apr 6, 2020

I was stuck trying to get this to work with docker on my MBP. I kind of made it work by removing the --net=host option since it won't work with macOS:

The host networking driver only works on Linux hosts, and is not supported on Docker Desktop for Mac, Docker Desktop for Windows, or Docker EE for Windows Server.

form 'Prerequisites' at: https://docs.docker.com/network/network-tutorial-host/

I managed to access node-red server by adding -p 1880:1880 option to map out node-red port. But I obviously can't see the sample switch accessory at the My Home app. I tried to map port 1881 as well and set the bridge node with that defined port with no luck.

Any suggestions? (of course Avahi is broken to, could solving that do the trick?)

Tanks,

@Shaquu
Copy link
Member

Shaquu commented Apr 8, 2020

@RaymondMouthaan would you help?

@RaymondMouthaan
Copy link

RaymondMouthaan commented Apr 9, 2020

Hi,

the '-p1880:1880' option only binds the internal Node-RED port with the external port, however this is not sufficient to use homekit. Unfortunately there is no solution other then '--net=host' - however this option doesn't work for Docker Desktop Windows and Mac, many discussions regarding this topic can be found on the internet. As far as I know there is no solution.

I recommend a Raspberry PI (or any other Linux based solution, like a Synology with Docker support) and run Docker there with node-red-contrib-homekit-bridged.

@R0dri
Copy link
Author

R0dri commented Apr 9, 2020

thanks for the reply. Can you asure that there is no other solution than the '--net=host' option? I think that avahi can be the main issue here but really can't tell. I tried to configure the bridge at the HomeKit node and set to port 1881 as well as exposing it with no luck.

Do you see any future to this? or wait until possibly docker adds support for macOS and windows as you said.

@RaymondMouthaan
Copy link

No I don't think it will ever solved ...

Some few links where you can find lots of discussion for quite some year about this topic:

So I don't think a solution to your issue will come soon ...

@crxporter crxporter added side topic How to use this and workarounds wontfix This will not be worked on labels Jun 30, 2020
@crxporter
Copy link
Member

Closing for now. If this still needs to be discussed please open a new issue on our docker repo

@Shaquu
Copy link
Member

Shaquu commented Oct 28, 2020

It sounds bad but NRCHKB (actually hap-nodejs) is intended to be used as a live service meaning on some kind of server machine.
It makes it work best on Linux flavoured systems. I am pretty sure most users are using Raspberry PI for that.
It is why Windows might not work good, and Mac OS will not work in Docker (yet?).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
side topic How to use this and workarounds wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

4 participants