Hubert Deng

Hey there, you're using a pretty old version of docker compose. Would you be able to upgrade that and try rerunning the script?

Got it, could you check the permissions of your clickhouse-server? I'm thinking this might be a similar issue to this here: https://github.com/ClickHouse/ClickHouse/issues/19223

are you able to perform a `docker exec -it sentry-self-hosted-clickhouse-1 sh`?

I still believe this is a permissioning issue where the clickhouse user cannot read the files

can you check the permissions of your `/clickhouse/config.xml` file?

this will be in the self-hosted directory

Yeah that looks like everyone has read access to the file, can you just run `chmod 755 ~/Downloads/self-hosted-22.7.0/clickhouse/config.xml` just to make sure and rerun `./install.sh`?

could also try ``` docker cp sentry-self-hosted-clickhouse-1:/etc/clickhouse-server/config.d/sentry.xml sentry.xml chmod 755 sentry.xml docker cp sentry.xml sentry-self-hosted-clickhouse-1:/etc/clickhouse-server/config.d/sentry.xml ```

note: Maybe M1 Max vs M1 Pro is causing issues with compatibility I have to comment out this for self-hosted to work on M1 Max in `docker-compose.yml` while Chad and...

Yep, that's what I was thinking. We should provide users the script to upgrade for a bit longer