You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "unaigarciarena (via GitHub)" <gi...@apache.org> on 2024/03/03 16:57:51 UTC
Re: [I] superset_init fails after upgrading to 3.0.0 due to alembic migrations misconfiguration [superset]
unaigarciarena commented on issue #25505:
URL: https://github.com/apache/superset/issues/25505#issuecomment-1975229630
I don't know if this has been solved, as it comes way too late. In my case, removing the volumes attached to the containers solved the issue.
I believe that certain database stored the docker id of a container for performing some action (in this case, "4b85906e5b91"), and, for some reason, it was made permanent. Because every docker compose uses the same volumes, every time I tried to start a fresh download, I kept getting the same error. I am not completely sure that this was the reason though.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org