• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Running Plesk in docker

quaylar

New Pleskian
Hello everybody,

Being a new Plesk user, I decided installing Plesk using the docker image available on the docker hub (plesk/plesk). I am not so sure that was a great idea. I did not pay attention to the command line parameters, but apparently there is no possibility to provide a volume for data to be persisted.

I have already installed a bunch of extensions and docker features (e.g. mail servers) and started to setup 1 domain. So - question to the pros here: Is anybody here executing plesk in a docker container on production systems? How do you ensure not losing your current configuration?
I cannot imagine that it is sufficient to simply have the container automatically restart on server reboot and regularly issuing a "docker commit" to persist the state into a new image?

Any tips highly welcome!

best,

--qu
 
I would not recommend using Plesk in docker in production. Only for some kind of tests, maybe.
 
Hello, plesk in docker should not be used in a production environment or for production purposes. It designed for integration (mainly API) testing and quick features overview without necessary VPS delegation and installation of a stand-alone product.
 
Hello,

Thank you for your reply! After digging around in this forum I kind of guessed/feared that. Unfortunate that there is no hint at all at the official docker hub page that this image is not meant to be used for production.

Do you know of any way I could export my current config, to import it into a new stand-alone installation? I would hate to go through the whole config process again.

regards,

qu
 
Back
Top