# Comment fonctionne la mise à jour du lanceur dans une configuration multi-conteneurs ?

**URL:** https://meta.discourse.org/t/how-does-launcher-update-work-in-multicontainer-setup/93388
**Category:** Self-hosting
**Tags:** two-container
**Created:** [Juillet 29, 2018, 5:08 UTC](https://meta.discourse.org/t/how-does-launcher-update-work-in-multicontainer-setup/93388 "2018-07-29T05:08:00Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![TheBestPessimist](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/thebestpessimist/32/247704_2.png) [@TheBestPessimist](https://meta.discourse.org/u/TheBestPessimist)
#### Post date: [Juillet 29, 2018, 5:08 UTC](https://meta.discourse.org/t/how-does-launcher-update-work-in-multicontainer-setup/93388/1 "2018-07-29T05:08:00Z")

</div>

Bonjour, longue suite de texte à venir, veuillez me pardonner, je suis simplement curieux.

Utilisateur de conteneurs doubles ici : data et web\_only.

Pour mettre à jour, je me connecte en SSH à mon serveur, puis j’imaginais que je devrais écrire :

```plaintext
sh /var/discourse/launcher bootstrap web_only
sh /var/discourse/launcher stop web_only
sh /var/discourse/launcher start web_only

```

Le problème en faisant cela est que, après le démarrage, j’ai toujours l’ancienne version en cours d’exécution, et non la version mise à jour.  
Pourquoi cela se produit-il ?

Pour qu’il soit mis à jour, je dois en fait exécuter :

```plaintext
sh /var/discourse/launcher bootstrap web_only
sh /var/discourse/launcher stop web_only
sh /var/discourse/launcher destroy web_only // aussi ceci
sh /var/discourse/launcher start web_only

```

Ma deuxième question est : pourquoi destroy ne supprime-t-il pas également mon image nouvellement amorcée ?

Une autre remarque intéressante : j’ai remarqué que pendant l’amorçage, plusieurs conteneurs différents sont créés et supprimés.

Pourriez-vous s’il vous plaît expliquer un peu (un peu plus ?) comment fonctionne launcher et quelles astuces il utilise ?

Merci d’avance.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [Juillet 30, 2018, 2:21 UTC](https://meta.discourse.org/t/how-does-launcher-update-work-in-multicontainer-setup/93388/2 "2018-07-30T02:21:50Z")

</div>

> [@TheBestPessimist](#):
>
> The problem by doing this is that after start I still have the previous version running, not the updated one.  
> Why is this happening?

Because “stop” just stops the current running container. You need to also remove it so you launch the new container you built.

> [@TheBestPessimist](#):
>
> My second question is: why does destroy not also delete my newly bootstrapped image?

“destroy” will destroy containers, not images. In docker speak this is the difference between `rm` and `rmi`

Bootstrap creates an “image”

Start will use the “image” to create a “container”

---

<div class="post-metadata">

### Author: ![TheBestPessimist](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/thebestpessimist/32/247704_2.png) [@TheBestPessimist](https://meta.discourse.org/u/TheBestPessimist)
#### Post date: [Juillet 30, 2018, 4:30 UTC](https://meta.discourse.org/t/how-does-launcher-update-work-in-multicontainer-setup/93388/3 "2018-07-30T04:30:34Z")

</div>

> [@sam](#):
>
> Start will use the “image” to create a “container”

\*only if a container doesn’t exist. If the container exists, then it will use the same one (even though it is not from the latest image). ← Is that correct?

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [Juillet 30, 2018, 5:06 UTC](https://meta.discourse.org/t/how-does-launcher-update-work-in-multicontainer-setup/93388/4 "2018-07-30T05:06:02Z")

</div>

> [@TheBestPessimist](#):
>
> \*only if a container doesn’t exist.

yes, that is correct. If the container exists already it will not create a new one.

---

<div class="post-metadata">

### Author: ![TheBestPessimist](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/thebestpessimist/32/247704_2.png) [@TheBestPessimist](https://meta.discourse.org/u/TheBestPessimist)
#### Post date: [Juillet 30, 2018, 5:17 UTC](https://meta.discourse.org/t/how-does-launcher-update-work-in-multicontainer-setup/93388/5 "2018-07-30T05:17:37Z")

</div>

Thanks for all the answers.

Do you think this post could be material for a howto post?

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [Juillet 30, 2018, 5:22 UTC](https://meta.discourse.org/t/how-does-launcher-update-work-in-multicontainer-setup/93388/6 "2018-07-30T05:22:53Z")

</div>

I think the knowledge should probably integrated into an existing howto about multi container setup.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [Août 29, 2018, 5:22 UTC](https://meta.discourse.org/t/how-does-launcher-update-work-in-multicontainer-setup/93388/7 "2018-08-29T05:22:54Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
