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.

  • Need to create listener for docker plugin on Jenkins on port 2375
  • How to cache node_modules on Docker build?
  • Check/connect to Redis running within docker from Java(Spring Boot) or Node.js
  • Docker-compose: Copying files from local env to EC2 instance
  • Adding tags to docker image from jenkins
  • Docker - Ubuntu - Nginx - MariaDB - Connection refused
  • 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        0.0.0.0:8080->8080/tcp, 0.0.0.0:8090->8090/tcp, 0.0.0.0:8180->8180/tcp    wasabi-main
    df6ac72359d7        mysql:5.6           "docker-entrypoint.sh"   6 days ago          Up 7 minutes        0.0.0.0:3306->3306/tcp                                                    wasabi-mysql
    4d7659ae5321        cassandra:2.1       "/docker-entrypoint.s"   6 days ago          Up 8 minutes        7000-7001/tcp, 0.0.0.0:9042->9042/tcp, 7199/tcp, 0.0.0.0:9160->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

  • Docker + MariaDB connection
  • Docker Akka-Http application endpoint not reachable
  • Install Docker in container for use by GitLab CI build
  • Vagrant and Docker provider: Container not loaded, Boot2Docker VM not available with SSH
  • Docker ElasticSearch 5 does not start . Even ELK does not start
  • Passing reports through docker in codecov gives error
  • 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.