table prefix bug?

[skironDotNet]

Here is the story to give you more background
I have OC 10.5 "normal" installation, so Apache/PHP everything works
Decided to go docker, created custom docker-compose based on official, just wan to use non-combo DB external dockerized mysql and don't want to use docker volumes just bare old-fashion volumes. Exported DB data to new DB
Spent like 16h already to make everything work lol. Have set all the permissions

The container started just fine, I have 'temp' user as env startup admin since existing 'admin' was in the DB
and the DB migration went fine (using OC latest 10.11)

First login as existing admin was fine but I see no files just a popup Directory “/” not found, ok looked in oc_storages, deleted dead entry.
Login again I see the file structure, but can't load anything

So I'm thinking let's login as 'temp' user created by the container on first start, this is what I get

So I'm searching online and found advice like run ./occ files:scan --all and the bug begins, complaining db_name.appconfig table doesn't exist

Well it doesn't because everything starts as oc_

and config confirms oc_ prefix

Why occ fired in the container is not using oc_ prefix?

Thanks for reading

[skironDotNet]

My bad, apparently I wasn't using proper way to use occ (the container thinking)
So did it this way https://doc.owncloud.com/server/next/admin_manual/installation/docker/#running-occ-commands
got more friendly error :)

[skironDotNet]

So based on this owncloud/core#25755 (comment) makes sense the 'home' column has old values from prev server

I guess the bug is in DB migration script, I think it should update that value based on datadirectory config

[xoxys]

That is still not a container issue. Please use the forum as suggested on your last issue already or continue in the owncloud/core issue.