V3 to V4 Migration: lookup redis on 127.0.0.53:53: server misbehaving

I am running a dockerized chirpstack 4. I have restored my db.out for the chirpstack 3 database and have run the following command.

./chirpstack-v3-to-v4 --cs-config-file ./chirpstack.toml  --as-config-file ./chirpstack-application-server.toml --ns-config-file ./chirpstack-network-server.toml --drop-tenants-and-users

Afterwards I see the following output:

2024/09/30 16:38:43 Reading ChirpStack configuration file: ./chirpstack.toml
2024/09/30 16:38:43 Reading AS configuration file: ./chirpstack-application-server.toml
2024/09/30 16:38:43 Start migration
2024/09/30 16:38:43 Deleting users and tenants from target database
2024/09/30 16:38:43 Migrating users
2024/09/30 16:38:43 Migrating organizations
2024/09/30 16:38:43 Migrating organization users
2024/09/30 16:38:43 Migrating applications
2024/09/30 16:38:43 Migrating application integrations
2024/09/30 16:38:43 Reading NS configuration file: ./chirpstack-network-server.toml
2024/09/30 16:38:43 Migrating region: EU868
2024/09/30 16:38:43 Migrating gateways
2024/09/30 16:38:43 Migrating gateway metrics
2024/09/30 16:38:43 Get gateway-metrics keys error: dial tcp: lookup redis on 127.0.0.53:53: server misbehaving

Upon looking at the chirpstack UI I can see my gateways and applications, but not the devices.

What can I do to ensure everything is copied over correctly?

It looks like it’s trying to resolve DNS (TCP, though?) using localhost from within your container or environment. That may not be correct.

I am running the migration script from the host machine so should it not be attempting to resolve localhost from my machine?

Just to test I did:

telnet 127.0.0.53 6379
Trying 127.0.0.53...
Connected to 127.0.0.53.
Escape character is '^]'.

and was able to connect