Digital Ocean has recently added support for Atomic Host, so i wanted to test it out, but now I'm facing problem with docker-machine and Fedora Atomic Host on Digital Ocean, when trying to create a machine via docker-machine create node1 -d digitalocean --digitalocean-access-token XXX-XXX --digitalocean-image fedora-25-x64-atomic
it can't provision docker since yum
is not present in atomic host and yet it is _called_ to install some packages (though any of them are already present), so basically Atomic Host is treated as a regular Fedora by docker-machine.
the docker-machine
command outputs the following error:
Running pre-create checks...
Creating machine... (manager)
Creating SSH key... (manager)
Creating Digital Ocean droplet... (manager)
Waiting for IP address to be assigned to the Droplet...
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 fedora...
Error creating machine:
Error running provisioning: something went wrong running an SSH command
command : sudo -E yum install -y curl
err : exit status 1
output : sudo: yum: command not found
cc @dustymabe
@cdrage, can you mark this as fixed by your PR when you open it?
@klud1 Please have a look at https://github.com/cdrage/machine/commit/80de5fc46cdeae5a852baac5c1d63b734fcf0034
Perhaps you can take it and create a PR for it? :) Let me know! I should be able to find some resources this week to work and test this out as well.
@dustymabe Do we still have use case for this provisioner? Should we create a PR, @cdrage current bit you have in place need to be updated with systemd drop in features.
@praveenkumar, I think it would be nice if docker-machine worked with atomic host. so, yes??
Most helpful comment
@praveenkumar, I think it would be nice if docker-machine worked with atomic host. so, yes??