I have found a working workaround (should have thought of it when I made the original comment):

Warning: This kinda breaksdocker compose watch in that it keeps re-adding those files back to the container, which then gets synced back to the host because of volume mapping, then triggerswatch's sync again... Only do this when you are creating a revision and revert the change once you are done.

Change the backend volume to include the alembic folder:

    volumes:      - ./backend/htmlcov:/app/htmlcov      - ./backend/app/alembic:/app/app/alembic

You could drill down more to only the versions folder.

I'm having this same issue. When I added those backend volumes, my docker didn't build so I still wasn't able to get it to work - see error message below. Can we make this into an issue?

Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "fastapi": executable file not found in $PATH: unknown (app)

@josephna76 It's been a while since I did that but I believe adding only the alembic folder (and not the whole backend folder) is how I solved it when I encountered that issue.

The drawback of this is that live reload of fastapi will not work. I am developing it locally in the meantime but yes, I would want this to be an issue as well. Looks like the maintainers are not actively looking at discussions anyway.

Try excluding the alembic folder from watch to fix the refresh

Great, thanks yohaoquan and meme8383! I tried your solutions and it seemed to work, but I went with the documented solution of using SQLModel directly without Alembic while this gets resolved.

I created this small script to expose the vars in .env so that the settings instance can work even when running locally.

# db_revision.shexport PYTHONPATH=$(pwd)# turn on auto-exportset -a# expose env vars in .envsource ../.env# turn off auto-exportset +a# revisionalembic revision --autogenerate -m "$1"

then u can do./script/db_revision "add column"

I did the steps you mentioned but I am getting this error
sqlalchemy.exc.OperationalError: (psycopg.OperationalError) connection failed: connection to server at "127.0.0.1", port 5432 failed: FATAL: password authentication failed for user "postgres" (Background on this error at: https://sqlalche.me/e/20/e3q8)

have you by any chance faced the same issue? I am sure of the credentials I checked them several times. Also the credentials work properly in the adminer login.

@adham404

best guess, you've missed to start the shell in the docker container?
docker compose exec -it backend bash.

Your script tries to connect to a database on your local machine on port 5432, but as far as I get thedocker-compose.yml, the port 5432 is never exposed outside the docker stack.