by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Joshua Spiewak
    @jspiewak
    lol
    Didip Kerabat
    @didip
    how would docker registry work with swarm if it uses more than 1 container? it store things in filesystem, no?
    Nicolas Degory
    @ndegory
    you can configure different backends
    s3 bucket for instance
    Didip Kerabat
    @didip
    ah
    Camilo Sanchez
    @camilin87
    In this example. The registry is running on a single node. If that node goes down. Will I still be able to access it at localhost:5000 on any other swarm node?
    Nicolas Degory
    @ndegory
    no
    Tony Pujals
    @subfuzion
    hehe nope
    Nicolas Degory
    @ndegory
    if you run is as a service, with a non local backend, you'll be able to access it (if more than one replica, or until a new task is created)
    devavrath
    @devavrath
    Does the builtin overlay networks use flannel?
    Didip Kerabat
    @didip
    is the network subcommand flexible enough to assign custom subnet, etc?
    Tony Pujals
    @subfuzion
    See this page to look into aspects / concerns of running / scaling your registry
    https://docs.docker.com/registry/deploying/#running-a-domain-registry
    @devavrath No ... but I do believe Docker worked with weave for it
    devavrath
    @devavrath
    cool!! thanks
    Didip Kerabat
    @didip
    whoa, in just 1 year docker changed so much :D
    Tony Pujals
    @subfuzion
    Docker 1.12/1.13/17.x represented a HUGE leap ... game changer as significant as 1.0, and really changes the need to consider a more complex framework for orchestration, like kubernetes
    Didip Kerabat
    @didip
    Will swarm autoscale the containers if some Docker nodes went down?
    Tony Pujals
    @subfuzion
    it will attempt to achieve the desired state
    Jeff Rosenbaugh
    @jeffrsnbgh_twitter
    Screen Shot 2017-06-20 at 3.00.11 PM.png
    Tony Pujals
    @subfuzion
    so yes, if you specified x number of replicas, it will attempt to recreate containers on remaining available nodes
    Jeff Rosenbaugh
    @jeffrsnbgh_twitter
    that doesn't seem right
    hshiraishi
    @hshiraishi
    better to have REGISTRY=127.0.0.1:5000 and TAG=v1 on the commands on page 148?
    Laura Frank
    @rheinwein
    workshop resumes at 3:30!
    victorpjulio
    @victorpjulio
    how do i connect to my instance on docker playground?
    Laura Frank
    @rheinwein
    you want to ssh into it or somesuch? the web browser is best, but there is a docker machine driver if you want something else: https://github.com/play-with-docker/docker-machine-driver-pwd
    Mark Garrison
    @garrmark
    my coin miner flatlined when I ran the docker service create --name rng --network dockercoins --mode global \
    --detach=false $REGISTRY/rng:$TAG but everyting appears to be running
    [ip-172-31-27-200] (local) docker@52.53.244.51 ~
    $ docker service ls
    ID NAME MODE REPLICAS IMAGE PORTS
    7kk6e1ccwk3l redis replicated 1/1 redis:latest
    of4lyei1dx34 hasher replicated 1/1 127.0.0.1:5000/hasher:v1
    phivtrd2ye2h registry replicated 1/1 registry:2 :5000->5000/tcp
    qhn22vbhk461 webui replicated 1/1 127.0.0.1:5000/webui:v1
    :8000->80/tcp
    wsekrt658omu rng global 5/5 127.0.0.1:5000/rng:v1
    zxeku7ip9h1z worker replicated 10/10 127.0.0.1:5000/worker:v1
    Rubén López
    @rubenclopez
    So what is the difference between docker run vs docker service ?
    Nicolas Degory
    @ndegory
    docker run creates and starts a container on your local docker engine
    Rubén López
    @rubenclopez
    oh docker service is swarm?
    Nicolas Degory
    @ndegory
    docker service creates a service on the swarm, and the orchestration will take care of scheduling tasks on the swarm
    right
    Rubén López
    @rubenclopez
    Got it. Thanks.
    Karl Girthofer
    @Kgirthofer
    does docker service have built in self-healing?
    Tony Pujals
    @subfuzion
    @rubenclopez Yes, to be clear you can use docker service create to create individual services and you can use docker stack deploy to deploy a whole stack of services, but this all relies on Docker swarm mode and that idea of services -> tasks/replicas -> containers
    @Kgirthofer Yes, in swarm mode, the scheduler attempts to maintain your desired state
    Laura Frank
    @rheinwein
    @Kgirthofer the docker service API is declarative, so swarm is constantly evaluating whether or not the actual state matches your desired state
    Karl Girthofer
    @Kgirthofer
    sweet
    Karl Girthofer
    @Kgirthofer
    all of that is configurable I presume?
    quantities of b/g
    i.e. 1000 containers, not going to b/g one at a time?
    Nicolas Degory
    @ndegory
    yes, deploy options in the compose file
    Karl Girthofer
    @Kgirthofer
    ah - as touched just now
    Don Ebben
    @debben
    When we built, pushed, and deployed again, how did swarm know that there was a change despite the image tag staying the same? Is there a "always pull" behaviour by default?
    Tony Pujals
    @subfuzion

    @Kgirthofer You can see docs for the compose options here:
    https://docs.docker.com/compose/compose-file/#deploy

    And service update command options here:
    https://docs.docker.com/engine/reference/commandline/service_update/

    Nicolas Degory
    @ndegory
    unlike docker run, when creating tasks swarm will try to pull if there's a new version of the image
    it checks the digest
    Tony Pujals
    @subfuzion
    @debben Docker actually always pulls
    in swarm mode each node will always pull the node image, the digest is used instead of the tag (which isn't necessarily the "latest" version with the same tag)