This image contains an SSH daemon and rsync, as well as the tool awake to send WoL packets.
Credit: panubo/docker-sshd
This image is based on panubo's docker-sshd image, with the sole addition of awake being installed. The itentended use case is to use this image as a service to SSH into from another container running a scheduler and waking up other machines on the network using awake.
- Docker Registry @ salvoxia/sshd-awake
- GitHub @ salvoxia/docker-sshd-awake
Build
docker build -t salvoxia/sshd-awake:latest .
Build Multi-Arch (buildx)
docker buildx create --name multi-platform-builder --platform linux/arm/v7,linux/arm64/v8,linux/amd64
docker buildx build --builder multi-platform-builder -t salvoxia/sshd-awake:latest .
Usually it is not possible to send UDP broadcasts from a docker container to the "outside world" if the container is not using host networking mode but the docker bridge. Using host networking mode might not possible or desirable for security reasons. As a workaround on Unix based host systems, it is possible to enable broadcast forwarding between the docker bridge and the bridged network interface. This script by dhutchison can be used to persistently enable broadcast forwarding for a specified docker network.
The broadcast address needs to be specified explicitly for the broadcast to be routed correctly. Specify the brocast address for the network the machine to be waken up is part of.
awake -b 192.168.1.255 AB:CD:EF:12:34:56