Cannot run npx supabase db reset in newly initialized project

[Silur]

Environment: Arch linux x64, supabase-cli 1.165.0

docker system prune -a # to reset all volumes and download latest images
mkdir /tmp/newproject
cd $_
npm install supabase
npx supabase init
npx supabase start
# services run successfully, realtime service healthcheck positive
npx supabase db reset --debug

Running an empty db reset as above results with the following:

** (ArgumentError) errors were found at the given arguments:

  * 1st argument: the table identifier does not refer to an existing ETS table

    (stdlib 4.3) :ets.lookup(:cachex_overseer_table, Realtime.Tenants.Cache)
    (cachex 3.4.0) lib/cachex/services/overseer.ex:89: Cachex.Services.Overseer.retrieve/1
    (cachex 3.4.0) lib/cachex.ex:676: Cachex.fetch/4
    (realtime 2.28.32) lib/realtime/context_cache.ex:12: Realtime.ContextCache.apply_fun/3
    (realtime 2.28.32) lib/realtime/tenants.ex:59: Realtime.Tenants.health_check/1
    nofile:1: (file)
error running container: exit 1

[Silur]

issue still present in version 1.172.2

[sweatybridge]

What's the output from supabase services?

[timobehrens]

I have a similar issue: I cannot clear my hosted DB using npx supabase db reset --linked. The databases are not deleted at all.

[sweatybridge]

I cannot clear my hosted DB using npx supabase db reset --linked

@timobehrens this sounds like a separate issue with hosted project. Could you file a support ticket so we can take a closer look?

[sweatybridge]

closing as not reproducible.