remove bound ports to host causing conflict and not required for comp…

…ose - was used by kompose

Changelog.rdoc

@@ -1,3 +1,7 @@
+==Ragios v0.7.2.1
+07-08-2019
+- Fix bug with that raises a port already bound error for workers port 5043 during started, this bug was introduced during the translation of existing docker-compose files to kubernetes for the last release. (showstopper release for v0.7.2 users)
+
 ==Ragios v0.7.2
 07-07-2019
 - Added support to easily run Ragios on a Kubernetes cluster and expose it via a load balancer

VERSION

@@ -1 +1 @@
-0.7.2
+0.7.2.1

docker-compose.yml

@@ -73,9 +73,6 @@ services:
     expose:
       - "5042"
       - "5043"
-    ports:
-      - "5042:5042"
-      - "5043:5043"
     tty: true
     stdin_open: true
     entrypoint: bundle exec ruby bin/recurring_jobs_ctl.rb run
@@ -102,8 +99,6 @@ services:
       AWS_SES_ENDPOINT:
       COUCHDB_ADMIN_USERNAME:
       COUCHDB_ADMIN_PASSWORD:
-    ports:
-      - "5043:5043"
     tty: true
     stdin_open: true
     entrypoint: bundle exec ruby bin/workers_ctl.rb run
@@ -122,8 +117,6 @@ services:
       COUCHDB_ADMIN_PASSWORD:
     expose:
       - "5045"
-    ports:
-      - "5045:5045"
     tty: true
     stdin_open: true
     entrypoint: bundle exec ruby bin/events_ctl.rb run
@@ -148,8 +141,6 @@ services:
       COUCHDB_ADMIN_PASSWORD:
     expose:
       - "5044"
-    ports:
-      - "5044:5044"
     tty: true
     stdin_open: true
     entrypoint: bundle exec ruby bin/notifications_ctl.rb run