Upgrading a service leads to Rancher losing persistence of environment variables

0 votes

I am using rancher-compose for upgrading my services. I  have set an environment variable and then I am running the compose command over the terminal. After the upgrade, the environment variable I initialized previously in the UI is not there anymore.

The rancher-compose command that I am using is:

rancher-compose -p [my_stack_name] --url ${RANCHER_ENDPOINT} --access-key ${ACCESS_KEY} --secret-key ${SECRET_KEY} up -d --pull --upgrade --confirm-upgrade
Can anyone help me with this?
Apr 27, 2018 in DevOps & Agile by Atul
• 10,240 points
• 2,418 views

1 answer to this question.

0 votes

when you upgrade, what it will do is, it will do the service match the definition in the compose file that is provided by you. If you are changing things in the UI and not changing your compose file, they will be gone.

I hope that it will let you resolve your problem.

answered Apr 27, 2018 by shubham
• 7,340 points

Related Questions In DevOps & Agile

0 votes
1 answer
0 votes
0 answers
0 votes
1 answer
0 votes
1 answer

I'm trying to create a simple service on kubernetes

Hi@Edureka, After you run the kubeadm init command ...READ MORE

answered Dec 21, 2020 in DevOps & Agile by MD
• 95,460 points
• 1,669 views
+5 votes
7 answers

Docker swarm vs kubernetes

Swarm is easy handling while kn8 is ...READ MORE

answered Aug 27, 2018 in Docker by Mahesh Ajmeria
• 10,701 views
+15 votes
2 answers

Git management technique when there are multiple customers and need multiple customization?

Consider this - In 'extended' Git-Flow, (Git-Multi-Flow, ...READ MORE

answered Mar 27, 2018 in DevOps & Agile by DragonLord999
• 8,450 points
• 10,138 views
+1 vote
2 answers