bbaranowski

Thank you so much for your help! I managed to successfully update my instance. Previously, I simply changed the release tag to 2026.2, did a docker pull, and ran the container, assuming the migration would happen automatically in the background. It was totally my mistake for not scrolling down to the very bottom of the Docker documentation. Ironically, I somehow ended up reading the upgrade instructions for Windows instead! :D

Everything is up and running perfectly now. Thanks again for pointing me in the exact right direction!

Thank you for your reply. I have just sent you a direct message with the requested information.

I also tried a step-by-step upgrade by pulling version 2026.1.22 first, but the exact same 'AccountExpirationDate' database error occurs. What should i do?

Upon reviewing my docker-compose.yml file, I noticed that the dvls_init container section is currently commented out. I suspect that this container is responsible for executing the database schema migrations (which would explain the missing AccountExpirationDate column and the groups issue).

Could you please confirm if the following procedure is the correct and sufficient way to perform this upgrade?

Restore my VM snapshot back to version 2025.3 (to have a consistent database).

Uncomment the dvls_init section in my docker-compose.yml.

Set the image tag to 2026.2.11 for both the dvls_init and dvls_server containers.

Run the dvls_init container first to upgrade the database schema.

Once the initialization is complete, start the main dvls_server container.

Will running the dvls_init container automatically handle the entire database migration from 2025.3 directly to 2026.2.11 without the need to go through intermediate versions

Hello,

I am writing to request your assistance regarding an issue we encountered while upgrading our Devolutions Server (hosted via Docker with an MS SQL database).

I recently attempted to upgrade our DVLS container directly from version 2025.3 to 2026.2.11. After starting the new container, we encountered the following database error:

Invalid column name 'AccountExpirationDate'

Additionally, as a result of this issue, all users were unexpectedly removed from their respective groups. It appears that there was a change in the database structure, but the schema migration did not execute properly.

Could you please advise on how to proceed?

To perform this upgrade correctly, is it necessary to upgrade step-by-step through all the intermediate versions, or should a direct upgrade handle the database migration automatically?

Thank you in advance for your support. I look forward to your guidance.