Giter VIP home page Giter VIP logo

Comments (5)

pascalandy avatar pascalandy commented on May 30, 2024

I could not create a cluster with public adresses but it's working using private adresses.

Using the CLI and docker-machine for scw it's solid. Here is how I do it:

docker-machine create -d scaleway \
--scaleway-region="par1" \
--scaleway-image="3803a8a7" \
--scaleway-token="123123123" \
--scaleway-organization="123123123" \
--scaleway-commercial-type="VC1S" \
--swarm \
--scaleway-name="N01-PAR1" N01-PAR1

3803a8a7 is the docker image

It's good to know the second name is used by the docker-machine driver.

from docker-machine-driver-scaleway.

pascalandy avatar pascalandy commented on May 30, 2024

Actually, more I'm thinking about it ...

We don't need --swarm as it makes more sense to go with the Docker Swarm Mode.


Create your nodes and then run this on your manager:

# scaleway (private address)
IP_N01=$(ifconfig eth0 | grep "inet addr" | cut -d ':' -f 2 | cut -d ' ' -f 1)
echo "On the manager run: docker swarm init --advertise-addr=$IP_N01"

from docker-machine-driver-scaleway.

pascalandy avatar pascalandy commented on May 30, 2024

@alexellis I don't think it's docker-machine's job to create a cluster.

from docker-machine-driver-scaleway.

chokosabe avatar chokosabe commented on May 30, 2024

The script above no longer seems to work; quite a few fails throughout:

sh start-swarm-cluster.sh

  • docker-machine create -d scaleway --swarm --swarm-master --scaleway-name=swarm-manager --swarm-discovery=token://my-token swarm-manager
  • docker-machine create -d scaleway --swarm --scaleway-name=swarm-node-1 --swarm-discovery=token://my-token swarm-node-1
  • docker-machine create -d scaleway --swarm --scaleway-name=swarm-node-2 --swarm-discovery=token://my-token swarm-node-2
  • docker-machine create -d scaleway --swarm --scaleway-name=swarm-node-3 --swarm-discovery=token://my-token swarm-node-3
    Running pre-create checks...
    Running pre-create checks...
    Creating machine...
    Creating machine...
    (swarm-manager) Creating SSH key...
    (swarm-node-1) Creating SSH key...
    Running pre-create checks...
    Creating machine...
    (swarm-node-2) Creating SSH key...
    Running pre-create checks...
    Creating machine...
    (swarm-node-3) Creating SSH key...
    (swarm-node-2) Creating server...
    (swarm-node-1) Creating server...
    (swarm-node-3) Creating server...
    (swarm-manager) Creating server...
    Error creating machine: Error in driver during machine creation: {"message": "Internal error", "type": "server_error"}
    Error creating machine: Error in driver during machine creation: {"message": "Internal error", "type": "server_error"}
    (swarm-node-2) Starting server...
    Waiting for machine to be running, this may take a few minutes...
    (swarm-manager) Starting server...
    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 ubuntu(systemd)...
    Installing Docker...
    Detecting operating system of created instance...
    Waiting for SSH to be available...
    Detecting the provisioner...
    Provisioning with ubuntu(systemd)...
    Installing Docker...
    Copying certs to the local machine directory...
    Copying certs to the remote machine...
    Setting Docker configuration on the remote daemon...
    Copying certs to the local machine directory...
    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 because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.

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 because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.

from docker-machine-driver-scaleway.

gardner avatar gardner commented on May 30, 2024

The docs are for pre docker engine 1.12. As of 1.12 docker swarm behaves differently and does not appear to require an external service like consul or etcd to manage distributed configurations.

from docker-machine-driver-scaleway.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.