-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[CI][Release] Verification jobs are failing due to curl failure #41007
Comments
It seems that |
raulcd
added a commit
to raulcd/arrow
that referenced
this issue
Apr 5, 2024
…bles from docker compose when using docker cli on archery docker
kou
pushed a commit
that referenced
this issue
Apr 5, 2024
…rom docker compose when using docker cli on archery docker (#41026) ### Rationale for this change Currently our verification jobs are failing due to environment variables not being correctly interpolated. docker compose expects a double `$$` sign on the command as explained here: https://docs.docker.com/compose/compose-file/12-interpolation/ When we use `ARCHERY_USE_DOCKER_CLI=1` we are using `docker run` instead of `docker compose run`. The behaviour of the command changes and we have to update change the environment variable. ### What changes are included in this PR? Use correct docker compose binary when using `docker cli` and remove double $$. ### Are these changes tested? Via archery ### Are there any user-facing changes? No * GitHub Issue: #41007 Authored-by: Raúl Cumplido <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
Issue resolved by pull request 41026 |
tolleybot
pushed a commit
to tmct/arrow
that referenced
this issue
May 2, 2024
…bles from docker compose when using docker cli on archery docker (apache#41026) ### Rationale for this change Currently our verification jobs are failing due to environment variables not being correctly interpolated. docker compose expects a double `$$` sign on the command as explained here: https://docs.docker.com/compose/compose-file/12-interpolation/ When we use `ARCHERY_USE_DOCKER_CLI=1` we are using `docker run` instead of `docker compose run`. The behaviour of the command changes and we have to update change the environment variable. ### What changes are included in this PR? Use correct docker compose binary when using `docker cli` and remove double $$. ### Are these changes tested? Via archery ### Are there any user-facing changes? No * GitHub Issue: apache#41007 Authored-by: Raúl Cumplido <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
tolleybot
pushed a commit
to tmct/arrow
that referenced
this issue
May 4, 2024
…bles from docker compose when using docker cli on archery docker (apache#41026) ### Rationale for this change Currently our verification jobs are failing due to environment variables not being correctly interpolated. docker compose expects a double `$$` sign on the command as explained here: https://docs.docker.com/compose/compose-file/12-interpolation/ When we use `ARCHERY_USE_DOCKER_CLI=1` we are using `docker run` instead of `docker compose run`. The behaviour of the command changes and we have to update change the environment variable. ### What changes are included in this PR? Use correct docker compose binary when using `docker cli` and remove double $$. ### Are these changes tested? Via archery ### Are there any user-facing changes? No * GitHub Issue: apache#41007 Authored-by: Raúl Cumplido <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
rok
pushed a commit
to tmct/arrow
that referenced
this issue
May 8, 2024
…bles from docker compose when using docker cli on archery docker (apache#41026) ### Rationale for this change Currently our verification jobs are failing due to environment variables not being correctly interpolated. docker compose expects a double `$$` sign on the command as explained here: https://docs.docker.com/compose/compose-file/12-interpolation/ When we use `ARCHERY_USE_DOCKER_CLI=1` we are using `docker run` instead of `docker compose run`. The behaviour of the command changes and we have to update change the environment variable. ### What changes are included in this PR? Use correct docker compose binary when using `docker cli` and remove double $$. ### Are these changes tested? Via archery ### Are there any user-facing changes? No * GitHub Issue: apache#41007 Authored-by: Raúl Cumplido <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
rok
pushed a commit
to tmct/arrow
that referenced
this issue
May 8, 2024
…bles from docker compose when using docker cli on archery docker (apache#41026) ### Rationale for this change Currently our verification jobs are failing due to environment variables not being correctly interpolated. docker compose expects a double `$$` sign on the command as explained here: https://docs.docker.com/compose/compose-file/12-interpolation/ When we use `ARCHERY_USE_DOCKER_CLI=1` we are using `docker run` instead of `docker compose run`. The behaviour of the command changes and we have to update change the environment variable. ### What changes are included in this PR? Use correct docker compose binary when using `docker cli` and remove double $$. ### Are these changes tested? Via archery ### Are there any user-facing changes? No * GitHub Issue: apache#41007 Authored-by: Raúl Cumplido <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
vibhatha
pushed a commit
to vibhatha/arrow
that referenced
this issue
May 25, 2024
…bles from docker compose when using docker cli on archery docker (apache#41026) ### Rationale for this change Currently our verification jobs are failing due to environment variables not being correctly interpolated. docker compose expects a double `$$` sign on the command as explained here: https://docs.docker.com/compose/compose-file/12-interpolation/ When we use `ARCHERY_USE_DOCKER_CLI=1` we are using `docker run` instead of `docker compose run`. The behaviour of the command changes and we have to update change the environment variable. ### What changes are included in this PR? Use correct docker compose binary when using `docker cli` and remove double $$. ### Are these changes tested? Via archery ### Are there any user-facing changes? No * GitHub Issue: apache#41007 Authored-by: Raúl Cumplido <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug, including details regarding any error messages, version, and platform.
Almost all verification jobs have failed with:
verify-rc-source-cpp-linux-almalinux-8-amd64
verify-rc-source-cpp-linux-conda-latest-amd64
verify-rc-source-cpp-linux-ubuntu-20.04-amd64
verify-rc-source-cpp-linux-ubuntu-22.04-amd64
verify-rc-source-csharp-linux-almalinux-8-amd64
verify-rc-source-csharp-linux-conda-latest-amd64
verify-rc-source-csharp-linux-ubuntu-20.04-amd64
verify-rc-source-csharp-linux-ubuntu-22.04-amd64
verify-rc-source-go-linux-almalinux-8-amd64
verify-rc-source-go-linux-conda-latest-amd64
verify-rc-source-go-linux-ubuntu-20.04-amd64
verify-rc-source-go-linux-ubuntu-22.04-amd64
verify-rc-source-integration-linux-almalinux-8-amd64
verify-rc-source-integration-linux-conda-latest-amd64
verify-rc-source-integration-linux-ubuntu-20.04-amd64
verify-rc-source-integration-linux-ubuntu-22.04-amd64
verify-rc-source-java-linux-almalinux-8-amd64
verify-rc-source-java-linux-conda-latest-amd64
verify-rc-source-java-linux-ubuntu-20.04-amd64
verify-rc-source-java-linux-ubuntu-22.04-amd64
verify-rc-source-js-linux-almalinux-8-amd64
verify-rc-source-js-linux-conda-latest-amd64
verify-rc-source-js-linux-ubuntu-20.04-amd64
verify-rc-source-js-linux-ubuntu-22.04-amd64
verify-rc-source-python-linux-almalinux-8-amd64
verify-rc-source-python-linux-conda-latest-amd64
verify-rc-source-python-linux-ubuntu-20.04-amd64
verify-rc-source-python-linux-ubuntu-22.04-amd64
verify-rc-source-ruby-linux-almalinux-8-amd64
verify-rc-source-ruby-linux-conda-latest-amd64
verify-rc-source-ruby-linux-ubuntu-20.04-amd64
verify-rc-source-ruby-linux-ubuntu-22.04-amd64
Component(s)
Continuous Integration, Release
The text was updated successfully, but these errors were encountered: