High Availability for Bluemix Secure Gateway Docker Client

Architecting a solution on Bluemix that will use the Secure Gateway service to connect to on-premise resources.
Trying to understand how to approach achieving a production high availability configuration for the Secure Gateway Client which runs inside a Docker contained provided by Bluemix.

How are others approaching HA for the SG Client?

  • Generate TLS certificates for Docker for Windows
  • Override FROM image's ENV in Dockerfile
  • using smart_open lib with a s3 docker image
  • Is it possible to use docker remote API in the same fashion as regular API?
  • Ports are blocked: Can't install Docker Universal Control Plane on Ubuntu
  • Docker CMD doesn't see installed components
  • Why it'll abort when I add `RUN ln -sf /dev/stderr /var/log/mysql/error.log` to mysql dockerfile?
  • nginx and php-fpm in Docker
  • docker mapping volume directory not showing up [closed]
  • docker swarm mode multiple services same port
  • Does “docker-compose down” invoke “docker stop” on each container?
  • Trigger automatic build on dockerhub when some package is updated in official repository
  • One Solution collect form web for “High Availability for Bluemix Secure Gateway Docker Client”

    Docker does support an auto-start functionality, but there is no built in support within Secure Gateway currently to take advantage of that. Our next release (1.3.0) will support native installers for Linux (Ubuntu, RHEL and SLES), which will be out last week this month. Once out, you could use the native installer, setup the auto-start facility and control your client using native upstart or systemD capabilities.

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