How can I access my container to fix a database migration issue?

You could try starting the container with a different command. Just add `bash` or `sh` at the end of your `docker run` command. If the container has an entry point, you'll need to overwrite that too.

You can override the container's startup command quite easily. Use `docker run -it bash` to start it in an interactive terminal. If you want it to keep running without issue, you could use `docker run sleep infinity`. This way, you can access the shell later with `docker exec -it bash`. If you're using Docker Compose, add `command: sleep infinity` under your service.

Are you trying to start the existing container? Make sure you're not trying to run a new instance on the same database unless you're sure your data is on a shared volume.

Make sure to check whether the database container or the application container is the one restarting. If it's a failed DDL migration, it shouldn't prevent the database from starting cleanly.