We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After pulling the latest image public.ecr.aws/supabase/storage-api:v1.6.7, and then running supabase db pull, I get this error:
public.ecr.aws/supabase/storage-api:v1.6.7
supabase db pull
Error: Cannot find module '/app/dist/scripts/migrate-call.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1145:15) at Module._load (node:internal/modules/cjs/loader:986:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:174:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] }
When I sh into the docker container, there is no script called /app/dist/scripts/migrate-call.js, only /app/dist/scripts/migrate.js
sh
/app/dist/scripts/migrate-call.js
/app/dist/scripts/migrate.js
supabase db pull --debug
I expect the function to work as normal
The text was updated successfully, but these errors were encountered:
🎉 This issue has been resolved in version 1.6.8 🎉
The release is available on GitHub release
Your semantic-release bot 📦🚀
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Bug report
Describe the bug
After pulling the latest image
public.ecr.aws/supabase/storage-api:v1.6.7
, and then runningsupabase db pull
, I get this error:When I
sh
into the docker container, there is no script called/app/dist/scripts/migrate-call.js
, only/app/dist/scripts/migrate.js
To Reproduce
supabase db pull
supabase db pull
, it should error outsupabase db pull --debug
, it should show the error aboveExpected behavior
I expect the function to work as normal
Screenshots
System information
The text was updated successfully, but these errors were encountered: