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?

  • container stopped being able to connect database container on same machine
  • How to make docker volume update automatically?
  • docker-compose service and the network
  • Docker for Windows Beta release notes and version history
  • Docker Container starting with mongo server
  • docker run with -p and a single port (instead of mapping)
  • How can I pass arguments to a docker container with a python entry-point script using command?
  • docker : container exited when using -v option
  • How to disallow push to docker repository
  • PHP docker best way. Build application inside or outside docker? [closed]
  • Windows container fails to reach Azure File Storage
  • How can you get Grunt livereload to work inside Docker?
  • 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.