Wasabi API over HTTPS instead of HTTP

I am trying to serve Wasabi API over HTTPS. Currently, it is HTTP only.

I have a very basic setup ( as described here https://github.com/intuit/wasabi ) running on Ubuntu 16.04 on Google Cloud.

  • Kubernetes multi-tier container application
  • Ansible cannot import docker-py even though it is installed
  • docker-compose run doesn't work in windows
  • npm install receiving type error when using docker
  • Deploying docker container of Kibana 4 with port-mapping on Mesos/Marathon
  • Generate random non-overlapping docker binding ports
  • It is accessible via http://example.com:8080 and that seems to be the only port that’s used for the API.

    $ docker ps output:

    CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                                                                     NAMES
    ad37f34cf204        wasabi-main         "entrypoint.sh wasabi"   7 minutes ago       Up 7 minutes>8080/tcp,>8090/tcp,>8180/tcp    wasabi-main
    df6ac72359d7        mysql:5.6           "docker-entrypoint.sh"   6 days ago          Up 7 minutes>3306/tcp                                                    wasabi-mysql
    4d7659ae5321        cassandra:2.1       "/docker-entrypoint.s"   6 days ago          Up 8 minutes        7000-7001/tcp,>9042/tcp, 7199/tcp,>9160/tcp   wasabi-cassandra

    I would be happy with both solutions, running both HTTP and HTTPS or HTTPS only.

    PS! example.com itself is available over HTTPS

  • Graylog docker container only binds when it listens to and not
  • is it reasonable to run docker processes under runit/daemontools supervision
  • Performance: Java in Docker [closed]
  • redis official docker image port exposure to windows
  • managing multiple swarm clusters
  • Using chef to set up apt repository
  • One Solution collect form web for “Wasabi API over HTTPS instead of HTTP”

    At the moment, the Jetty container (wasabi-main) only serves HTTP traffic, and is not set up to serve HTTPS. What we usually do to serve HTTPS is place an Apache/Nginx proxy in front that does SSL termination, and then forwards the non-ssl request to Jetty.

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