### Steps to reproduce * Generate a new Rails application * Connect the Rails application to a non-Rails database with an existing structure and data (specifically without a `schema_migrations` table) * Generate a `schema.rb` file for it * Launch the application as a docker container against a copy of the database without the Rails `schema_migrations` table (but with data) ### Expected behavior The data in the database will be preserved. ### Actual behavior [This line in the generated docker-entrypoint](https://github.com/rails/rails/blob/15ddce90583bdf169ae69449b42db10be9f714c9/railties/lib/rails/generators/rails/app/templates/docker-entrypoint.tt#L12) will ultimately call [this line from the Rake task](https://github.com/rails/rails/blob/15ddce90583bdf169ae69449b42db10be9f714c9/activerecord/lib/active_record/tasks/database_tasks.rb#L672) because the schema migrations table is missing. This will then drop and recreate the database, losing all data in the existing database. ### System configuration **Rails version**: 7.2.1 **Ruby version**: 3.2.5