Skip to content
New issue

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

db test fails on Bitbucket CI with cli release v1.200.3 #2703

Closed
etzelc opened this issue Sep 24, 2024 · 2 comments · Fixed by #2705
Closed

db test fails on Bitbucket CI with cli release v1.200.3 #2703

etzelc opened this issue Sep 24, 2024 · 2 comments · Fixed by #2705
Assignees

Comments

@etzelc
Copy link
Contributor

etzelc commented Sep 24, 2024

Describe the bug
PR #2683 added security-opt flag to the run of pg_prove container. security-opt is not allowed on Bitbucket Cloud CI (see https://support.atlassian.com/bitbucket-cloud/docs/run-docker-commands-in-bitbucket-pipelines/#Full-list-of-restricted-commands).

One idea to fix this issue: Special treatment for Bitbucket CI like here

// Skip named volume for BitBucket pipeline

To Reproduce
Steps to reproduce the behavior:

  1. Run pipeline with supabase db tests on Bitbucket Cloud

Expected behavior
Tests are executed.

Error Log

3.36: Pulling from supabase/pg_prove
...
failed to create docker container: Error response from daemon: authorization denied by plugin pipelines: --security-opt is not allowed

Additional context

  • Version of supabase-cli v1.200.3
@etzelc etzelc changed the title db test fails on Bitbucket CI with cli release v1.200.3 db test fails on Bitbucket CI with cli release v1.200.3 Sep 24, 2024
@avallete avallete self-assigned this Sep 24, 2024
@avallete
Copy link
Contributor

Thank's for reporting, a fix in on it's way ! 👍

@etzelc
Copy link
Contributor Author

etzelc commented Sep 24, 2024

Thanks for the super fast fix. The preview release v1.201.1 is working as expected. 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants