Update process of Mautic using this image

[Norbell]

Hello,

since a few days I'm struggling wit the update path/process of this image and Mautic.
We needed to upgrade from Mautic2 to Mautic3. I did the following:

• I adjusted the image tag from [2.13-apache to v3-apache
• added the environment variable MAUTIC_VERSION=3.1.2
• and added the environment varialbe MAUTIC_RUN_MIGRATIONS=true

I used the same volume, I already used for mautic2.
After everything started up, successfully I get redirected to the installer of of mautic.
Then I go through the installer and after that all my data are gone.

Is this the intended behaviour?

Is this docker image more meant as a prebuild environment for running mautic?

How is the environment variable MAUTIC_VERSION meant to work?
What does changing this variable trigger?

I'm really confused. :)

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[ilkkao]

Docker/kubernetes is very popular nowadays. Would be great to hear how the updates are supposed to be done.

[noellarkin]

I used mautic/mautic:latest and ended up getting mautic v2.16.5....

[francoisauclair911]

Note that during the 4.0.x period, the 'mautic/mautic:latest' tag still refers to Mautic 2 for backward compatibility. If you intend to use Mautic 2, use the 'mautic/mautic:v2' tag instead of 'mautic/mautic:latest'.

https://hub.docker.com/r/mautic/mautic

I think that's why

[noellarkin]

I'm already running mautic/mautic:latest on Docker. How do I go about updating to the latest docker image (4.x)? Are there breaking changes?

[mollux]

@Norbell
The M5 images removed that confusion, as they became stateless (no more fiddling with the MAUTIC_VERSION, but the common practice to change the base image), see #238 and https://hub.docker.com/r/mautic/mautic

@noellarkin @ilkkao I created a separate issue to define the usage of the latest tag, as the current setup is indeed confusing, see #250