Open greylurk opened 8 years ago
They also contributed a lot to integrate docker on raspbian directly, which is now available in the APT repo, so hypriot-os is not stricly required anymore :)
There is a PR on its way for a raspbian provisioner (#3605), looks good but it's blocked for now because of a small quirk related to systemd config.
If I patch /etc/os-release, I get a little further with hypriotos-rpi-v1.4.0, but I still hit this subsequently:
$ docker-machine create --driver generic --generic-ip-address=192.168.88.72 --generic-ssh-user pirate zpi3
Running pre-create checks...
Creating machine...
(zpi3) No SSH key specified. Assuming an existing key at the default location.
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with debian...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Error creating machine: Error running provisioning: ssh command error:
command : sudo systemctl -f start docker
err : exit status 1
output : Job for docker.service failed. See 'systemctl status docker.service' and 'journalctl -xn' for details.
up
Maybe this issue should be renamed to something more generic.
The fact that ID_LIKE
is not used as fallback is just clearly wrong.
Would be great to see this fixed.
Just bumped to this too, would love to see the solution @tcurdt proposed implemented.
Still an issue in 2020.
If ID_LIKE=debian
is specified, my one-liner PR should solve the issue. Hopefully it's merged and we can use docker-machine with debian-like distros.
The folks over at http://blog.hypriot.com/ have built a custom raspbian-based distro which makes it easy to stand up a docker host on the Raspberry PI (and a few other ARM devices). However, when I try to add one of the new items to docker-machine, I get an "OS Type Unrecognized" error:
If I edit the "ID=" field in /etc/os-release on the raspberry pi to read "ID=debian" instead of "ID=raspbian" then it works fine, so the fix might be to fall back to the ID_LIKE if the ID field isn't recognized, but I'm not sure how that affects other debian derivatives