Error creating stack using docker-compose.yml and rancher-compose.yml

Archive Rancher 1.x
1

I ran an export of the config from a stack later I deleted the stack and I recreated it using docker-compose.yml and rancher-compose.yml from the Rancher console and it gives me an error “Failed to find existing service: Merchanweb)”.

rancher-compose.yml

version: '2’
services:
merchanapiback:
health_check:
response_timeout: 2000
healthy_threshold: 2
port: 18202
unhealthy_threshold: 3
initializing_timeout: 60000
interval: 2000
strategy: recreate
request_line: GET “/ping” "HTTP/1.0"
reinitializing_timeout: 60000
merchanapibacklb:
lb_config:
certs: []
port_rules:
- priority: 1
protocol: http
service: merchan/merchanapiback
source_port: 18202
target_port: 18202
health_check:
response_timeout: 2000
healthy_threshold: 2
port: 42
unhealthy_threshold: 3
interval: 2000
merchanapiservicelb:
lb_config:
certs: []
port_rules:
- priority: 1
protocol: http
service: merchan/merchanapiservice
source_port: 18203
target_port: 18203
health_check:
response_timeout: 2000
healthy_threshold: 2
port: 42
unhealthy_threshold: 3
interval: 2000
merchanapiservice:
health_check:
response_timeout: 2000
healthy_threshold: 2
port: 18203
unhealthy_threshold: 3
initializing_timeout: 60000
interval: 2000
strategy: recreate
request_line: GET “/ping” "HTTP/1.0"
reinitializing_timeout: 60000
merchanweb:
health_check:
response_timeout: 2000
healthy_threshold: 2
port: 18201
unhealthy_threshold: 3
initializing_timeout: 60000
interval: 2000
strategy: recreate
request_line: GET “/ping” "HTTP/1.0"
reinitializing_timeout: 60000
merchanweblb:
lb_config:
certs: []
port_rules:
- priority: 1
protocol: http
service: merchan/merchanweb
source_port: 18201
target_port: 18201
health_check:
response_timeout: 2000
healthy_threshold: 2
port: 42
unhealthy_threshold: 3
interval: 2000

docker-compose.yml

version: '2’
services:
merchanapiback:
image: qideia/merchanapiback
environment:
APORT: '18202’
MONGO: DB:10200/MERCHAN
HTTPSERVER: 'TRUE’
MERCHANTOKEN:***************************xM2FmM2MTR4NS4
stdin_open: true
tty: true
labels:
io.rancher.container.pull_image: always
io.rancher.scheduler.global: 'true’
merchanapibacklb:
image: rancher/lb-service-haproxy:v0.4.2
ports:
- 18202:18202/tcp
labels:
io.rancher.container.agent.role: environmentAdmin
io.rancher.container.create_agent: 'true’
io.rancher.scheduler.global: 'true’
merchanapiservicelb:
image: rancher/lb-service-haproxy:v0.4.2
ports:
- 18203:18203/tcp
labels:
io.rancher.container.agent.role: environmentAdmin
io.rancher.container.create_agent: 'true’
io.rancher.scheduler.global: 'true’
merchanapiservice:
image: qideia/merchanapiusuario
environment:
APIGEEURL: https://apigateway.com.br/v1
CODIGOSISTEMA: '3808’
APIGEEAUTHTOKEN: Bearer ***********AiF2wAnGWGgx
HTTPSERVER: 'TRUE’
MERCHANTOKEN:***************5NGExM2FmM2MTR4NS4
APORT: '18203’
stdin_open: true
tty: true
labels:
io.rancher.container.pull_image: always
io.rancher.scheduler.global: 'true’
merchanweb:
image: qideia/merchanweb
environment:
MERCHANTOKEN:*********GExM2FmM2MTR4NS4
URLAPIUSUARIO: http://IP:18203/merchan/api/v1
URLAPITIROCERTO: http://IP:18202/merchan/api/v1
PORT: '18201’
HTTPSERVER: 'TRUE’
stdin_open: true
tty: true
labels:
io.rancher.container.pull_image: always
io.rancher.scheduler.global: 'true’
merchanweblb:
image: rancher/lb-service-haproxy:v0.4.2
ports:
- 18201:18201/tcp
labels:
io.rancher.container.agent.role: environmentAdmin
io.rancher.container.create_agent: 'true’
io.rancher.scheduler.global: ‘true’

2

Having a similar issue. Did you find a fix? anyone else with thoughts?

3

I was facing the same issue. You should not qualify your service with the stack’s name in your rancher-compose.yml, like:
lb_config:
…
service: merchanweb

Once the stack is created, it will automatically prefixed with the stack’s name.

4

This is already fixed in Rancher v1.2.1. If you exported a stack that had a load balancer pointing to a service in the stack, it was prefixed with the stack name in the port rules of the load balancer.

https://github.com/rancher/rancher/issues/6829

5

Fixed thanks Denise… I upgraded to version 1.2.1-rc3