Resolved Docker engine package update

[Tigzy]

Hello,
On Onyx version, after the Docker engine package update (made through the UI) the containers are left stopped. It would be great if you could restart them automatically.

Thanks,

 

[SibProgrammer]

You can enable "automatic start on system reboot" option for specified container. See screenshot for details:

 

[Tigzy]

Thanks, I saw it but never thought using it that way
Quick question, is Plesk Onyx officially released yet? (since the beta feedback has been closed)

 

[Tigzy]

I just saw my mongodb has been lost after the container restart
Is it a normal thing? How to avoid this?

EDIT: nvm, I found this: http://stackoverflow.com/questions/18473409/how-to-persist-mongodb-data-between-container-restarts

 

[SibProgrammer]

Quick question, is Plesk Onyx officially released yet? (since the beta feedback has been closed)

Yes, it is.

 

[Tigzy]

Super, thanks.

 

[Tigzy]

One last question, is Onyx on production link for the installer? (one-click-installer).
Cause I'm trying it, but without the --tier testing it refuses to install on a Ubuntu 16.04
(Error like No id for "plesk" or something)

 

[SibProgrammer]

Release build is already available (for early adopters, partners and etc.), but official announcement will be in the beginning of November (GA). Then one-click-installer will be switched to install Plesk Onyx by default. Right now you could use "--tier current" option to install Onyx using one-click installer.

 

[Tigzy]

Thanks