Virtuozzo Application Platform 5.8.5

This document is preliminary and subject to change.

In this document, you will find all of the new features, enhancements and visible changes included to the PaaS 5.8.5 release.

Custom Docker Images with BusyBox support

Added support for custom Docker images with the BusyBox utilityLearn more

Software Stack Versions

Actualized list of supported OS templates and software stack versionsLearn more

Fixes Compatible with Prior Versions

Bug fixes implemented in the current release and integrated to the previous platform versions through the appropriate patchesLearn more

Bug Fixes

List of fixes applied to the platform starting from the current releaseLearn more

Custom Docker Images with BusyBox Support

BusyBox is a minimalistic software suite that replaces basic functions of more than 300 common commands. However, when installing a custom Docker image with BusyBox at the platform, the lack of functionality compared to the original tools affects the operability of the platform services (e.g. logs and file managers). Thus, in the current 5.8.5 PaaS release, support of the custom Docker images was extended to include templates with the BusyBox utility. Namely, all the additionally required tools are installed as a part of the container after-creation process.

Back to the top

Fixes Compatible with Prior Versions

Below, you can find the fixes that were implemented in the PaaS 5.8.5 release and also integrated into previous platform versions by means of the appropriate patches.

PaaS 5.8.5
#Compatible fromDescription
JE-532473.3The master node should always be selected when issuing the Let’s Encrypt certificate for the load balancer layer
JE-533955.0.5The /var/www/icons and /var/www/error directories are absent on the Apache PHP nodes
JE-508355.4The Install button should be locked with a warning during the Docker Swarm Cluster package installation if account limits are insufficient

Back to the top

Software Stack Versions

The software stack provisioning process is independent of the platform release, which allows new software solutions to be delivered as soon as they are ready. Herewith, due to the necessity to adapt and test new stack versions, there is a small delay between software release by its respective upstream maintainer and integration into the platform.

The most accurate and up-to-date list of the certified software stack versions can be found on the dedicated documentation page.

More info

Back to the top

Bug Fixes

In the table below, you can see the list of bug fixes applied to the platform starting from PaaS 5.8.5 release:

PaaS 5.8.5
#Description
JE-41739An error occurs when deploying and removing contexts simultaneously
JE-49773An error occurs when removing a custom domain attached to an environment
JE-52426The first HTTP request fails after binding custom domain to an environment without an external IP address
JE-52536Separate error codes should be provided for the failures during the service restart/stop/start/reload commands
JE-53367The appid alias does not work for the envName parameter for the ChangeTopology API method
JE-53503In case of a redeploy failure, the image snapshot should be removed after a successful rollback
JE-53519Personal access tokens require permissions for the Eval method to be used in JPS
JE-53539New limits should be applied immediately after an account upgrade without an obligatory refresh of the dashboard
JE-53575An empty Hub URL line is displayed in the after-creation email for custom Docker containers
JE-53601An error occurs when downloading files from the dashboard

Back to the top