# V1.21 to v1.22 upgrade - Expect database to use collation: utf8mb4\_0900\_as\_cs

**URL:** <https://forum.gitea.com/t/v1-21-to-v1-22-upgrade-expect-database-to-use-collation-utf8mb4-0900-as-cs/9251>\
**Category:** Install/Maintain/Configure\
**Created:** [June 1, 2024, 2:02pm UTC](https://forum.gitea.com/t/v1-21-to-v1-22-upgrade-expect-database-to-use-collation-utf8mb4-0900-as-cs/9251 "2024-06-01T14:02:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MichaelC](https://avatars.discourse-cdn.com/v4/letter/m/82dd89/32.png) [@MichaelC](https://forum.gitea.com/u/MichaelC)\
**Post date:** [June 1, 2024, 2:02pm UTC](https://forum.gitea.com/t/v1-21-to-v1-22-upgrade-expect-database-to-use-collation-utf8mb4-0900-as-cs/9251/1 "2024-06-01T14:02:57Z")

</div>

Upgraded from 1.21 to 1.22 using MySQL 8 in docker compose environment.  
There is no CHARSET defined in app.ini.

I’m seeing…

 ![ksnip_20240601-095738](https://us1.discourse-cdn.com/flex020/uploads/gitea/original/2X/0/03a2bc4dc6e931e332aecbd1084570af966125d4.png)

I would like to know how to run `gitea doctor convert` - when I attach to gitea container it says I can’t run gitea as root.

Can someone let me know how to run this gitea command or modify MySQL database? Does it apply to some or all tables?

The FAQs and searches dont seem to have quite enough detail… and not sure how to run gitea command line in a docker compose based deployment.

Thx.

---

<div class="post-metadata">

**Author:** ![alatnet](https://avatars.discourse-cdn.com/v4/letter/a/a8b319/32.png) [@alatnet](https://forum.gitea.com/u/alatnet)\
**Post date:** [August 5, 2024, 1:06pm UTC](https://forum.gitea.com/t/v1-21-to-v1-22-upgrade-expect-database-to-use-collation-utf8mb4-0900-as-cs/9251/2 "2024-08-05T13:06:14Z")

</div>

> docker exec -it bash  
> su git  
> gitea doctor convert

The key is to sign into another user that doesnt have root using su before executing the doctor command.