Hi Marcelo,
My apologies, I misunderstood the issue you were describing and the target version.
If you are trying to upgrade in place, there may be issues as we have upgraded the MySQL version from 5.7 to 8.0 between versions 2.5 and 2.6. The easiest solution will be to install a newer version of the Docker Compose environment and migrate your data.
If you have done this, then it's likely that you will need to perform some of the maintenance tasks associated with the upgrade process to ensure that your AtoM 2.5.3 / MySQL 5.7 data can be properly loaded into your 2.6/MySQL 8.0 database.
The commands and locations will be slightly different in the Docker environment (e.g. they will generally be preceded by docker compose exec etc), and I do not regularly use this environment so I can't provide the exact commands in all cases, but I have shared a very similar process recently for upgrading the Vagrant environment here that may be useful as a general guide:
You can also review the Upgrading instructions in our documentation here:
I think that you will need to:
- Ensure you have a backup of any data you want to keep as a sqldump outside of AtoM
- Use the purge command to clear your data
- Drop and recreate the database
- Load your sqldump
- Run the upgrade task
- Restart services and then try to repopulate the search index
After this, the version should be reflected properly in the settings, and your data should load properly. Hopefully this might help with the ES error you have encountered as well.
If you don't need to preserve any data (since the Docker environment is intended for development, and not for use in production), then hopefully the process should be much simpler.
Let us know how it goes and what you find!