Ping and Windows shutdown from Synology NAS on Docker

[fluffy-critter]

I'm having a couple of issues when running Homebridge-WOL from a Docker container on my Synology NAS.

The first one is that for whatever reason, the ping command is unable to execute; from the Terminal I get an error:

homebridge@attache:/volume1/homebridge $ ping 192.168.0.8
ping: socket: Operation not permitted

I'm guessing that there's something I need to do to set the ping command SetUID or the like, but I'm not particularly versed in Docker. The CLI ping tool from the NAS itself works fine, but I'm not sure which binary is being seen by Docker in this case.

The other issue that's even more puzzling is that my Windows machine is unable to shut down. When I try shutting down from HomeKit, no error appears in the Homebridge log. If I issue the same shutdown command from the Homebridge terminal, it works fine; I see:

homebridge@attache:/volume1/homebridge $ net rpc shutdown -I 192.168.0.8 -U (username)%(password)

Shutdown of remote machine succeeded

and the machine shuts down pretty much right away, as expected.

I'm guessing that the execution path seen by the terminal is different than that seen by the Homebridge parent process. I tried configuring the plugin to use the full path to the net command (/usr/local/bin/net according to which net from the terminal) but that didn't change things at all.

Has anyone managed to get this working on a Synology under Docker?

[fluffy-critter]

Okay, I figured out that /bin/ping was coming from the Synology file system, and just wasn't setUID like it was supposed to be. sudo chmod 5755 /bin/ping fixed that.

I'm still at a loss for why /usr/local/bin/net shutdown is only working from the terminal and not from the plugin itself, though.

[fluffy-critter]

Now it seems to be working for shutdown as well. I have no idea what changed. I wish I could post a more satisfying resolution for anyone else searching for this issue.