How I use a local container in a swarm cluster

A colleague find out Docker and want to use it for our project. I start to use Docker for test. After reading an article about Docker swarm I want to test it.

I have installed 3 VM (ubuntu server 14.04) with docker and swarm. I followed some How To ( and My cluster work. I can launch for exemple a basic apache container (the image was pull in the Docker hub) but I want to use my own image (an apache server with my web site).

  • Can't CD into directory with 755 permissions?
  • Where does the convention of using /healthz for application health checks come from?
  • How to get Container Id of Docker in Jenkins
  • How can I terminate a Docker instance from within itself?
  • Managing remote docker machines from multiple development machines
  • Celery workers in a docker swarm or rancher cattle
  • I tested to load an image (after save it in a .tar) but this option isn’t supported by the clustering mode, same thing with the import option.

    So my question is : Can I use my own image without to push it in the Docker hub and how I do this ?

  • Is there any way to provide Run parameters to a docker container image when starting a container from openstack nova?
  • How can JVMs running inside Bluemix container groups be monitored?
  • Running openshift origin on mac 10.11.6 with docker version 1.12.0
  • Tomcat + MySQL docker container outputting utf8 text with wrong encoding
  • Docker impossible to link nginx container with php-fpm container
  • dashDB local MPP deployment issue - cannot connect to database
  • One Solution collect form web for “How I use a local container in a swarm cluster”

    If your own image is based on a Dockerfile that you build you can execute the build command on your project while targeting the swarm.

    However if the image wasn’t built, but created manually you need to have a registry in between that you can push to, either docker hub or some other registry solution like

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.