Galaxy container can't spin up before migration starts?

Has anyone run into a problem using peroclate migrations on galaxy?

I push a new version to galaxy, the migration starts, but it seems like the container is stuck trying to spin up. Additionally, my migratio, which involves parsing CSVs and inserting them into the DB, is taking forever-- like 3 hours to parse 30k rows from a CSV. So something is definitely going wrong. I have another strategy for uploading CSVs manually, which runs through the same parsing script, and that is parsing and inserting much much faster… about 100k rows in 20 minutes (there is alot of parsing admittedly).

Has anyone else seen this behavior before?