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?

  • Docker login problems
  • nginx docker-image not reachable
  • Calling docker commands from jenkins job as step running outside docker VM
  • Docker scaling containers on a single host
  • Configuration issue in nginx of docker - Troubleshooting docker with no instaces
  • Docker receiving multicast traffic
  • Change volume configuration in docker-compose without losing the data
  • how does 'tar cv --files-from /dev/null | docker import - scratch' work?
  • Find out to which removed docker container a volume belonged to
  • Building a docker image using AWS Developer Tools
  • How to connect microservice to SQS/SNS
  • .ebextensions with Docker on elasticbeanstalk
  • 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.