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?
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
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