# \[Rancher-Compose\] Questions

**URL:** <https://forums.suse.com/t/rancher-compose-questions/3754>\
**Category:** Rancher 1.x\
**Created:** [August 20, 2016, 5:02pm UTC](https://forums.suse.com/t/rancher-compose-questions/3754 "2016-08-20T17:02:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![SJC](https://avatars.discourse-cdn.com/v4/letter/s/e5b9ba/32.png) [@SJC](https://forums.suse.com/u/SJC)\
**Post date:** [August 20, 2016, 5:02pm UTC](https://forums.suse.com/t/rancher-compose-questions/3754/1 "2016-08-20T17:02:06Z")

</div>

I am struggling to find answers for some questions I have on rancher-compose.

First of all can you perform a rolling upgrade of a service and keep the same service name? I have managed to upgrade (with issues) using: rancher-compose -p stack1 upgrade web web1 -c  
but I would like to keep the same service name, so I can execute this command in CI.

I have not seen any evidence of this implementation so if this is not possible can rancher-compose update the service name, like the API can?

As I mentioned above performing the rolling upgrade did have its issues, when executing “rancher-compose -p stack1 upgrade web web1 -c” it always fails half way through with the issue “FATA[0000] Put http://: net/http: invalid header field value “\v” for key Content-Length”. Re-running the command completes the upgrade successfully, is this a known issue or a new bug which I should report?

---

<div class="post-metadata">

**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\
**Post date:** [August 22, 2016, 9:23pm UTC](https://forums.suse.com/t/rancher-compose-questions/3754/2 "2016-08-22T21:23:33Z")

</div>

It sounds like you are looking for an “in service upgrade”.

[http://docs.rancher.com/rancher/v1.2/en/cattle/rancher-compose/upgrading/#in-service-upgrade](http://docs.rancher.com/rancher/v1.2/en/cattle/rancher-compose/upgrading/#in-service-upgrade)

---

<div class="post-metadata">

**Author:** ![SJC](https://avatars.discourse-cdn.com/v4/letter/s/e5b9ba/32.png) [@SJC](https://forums.suse.com/u/SJC)\
**Post date:** [August 23, 2016, 7:49pm UTC](https://forums.suse.com/t/rancher-compose-questions/3754/3 "2016-08-23T19:49:17Z")

</div>

Thanks for the suggestion, I have attempted to do the same as the “In Service Upgrade” details, however I get an error and then it just hangs, see the error details below.

My Stack is called “rancher” with the service name “web”.

Executed: `rancher-compose up --upgrade web`

```auto
    POST http://<Address>/v1/containers/1i172/?action=logs
    Request => null
    ERRO[0000] Failed to get logs for rancher_web_1: Post http://<Address>/v1/containers/1i172/?action=logs: net/http: invalid header field value "\x04" for key Content-Length 
    POST http://<Address>/v1/containers/1i173/?action=logs
    Request => null
    ERRO[0000] Failed to get logs for rancher_web_2: Post http://<Address>/v1/containers/1i173/?action=logs: net/http: invalid header field value "\x04" for key Content-Length 
    POST http://<Address>/v1/containers/1i174/?action=logs
    Request => null
    ERRO[0000] Failed to get logs for rancher_web_3: Post http://<Address>/v1/containers/1i174/?action=logs: net/http: invalid header field value "\x04" for key Content-Length

```

---

<div class="post-metadata">

**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\
**Post date:** [August 24, 2016, 5:55am UTC](https://forums.suse.com/t/rancher-compose-questions/3754/4 "2016-08-24T05:55:59Z")

</div>

Can you provide your original docker-compose.yml and rancher-compose.yml as well as the upgraded ones?