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.

Sign up for GitHub

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

Jump to bottom

[Developer Tools] Support passing through memory limits in archery docker run #28962

Closed
asfimport opened this issue Jul 7, 2021 · 2 comments
Closed

[Developer Tools] Support passing through memory limits in archery docker run #28962

asfimport opened this issue Jul 7, 2021 · 2 comments
Assignees
@lidavidm
Labels
Component: Archery Component: Developer Tools Type: enhancement
Milestone
5.0.0

Comments

@asfimport
Copy link
Collaborator

It can be useful to limit the memory available to one of our Docker containers to more accurately reproduce CI conditions. docker-compose doesn't directly support this (except in 'swarm' deployment mode) but since Archery can directly invoke the docker CLI, we could support this ourselves, either by adding custom metadata into docker-compose.yml or exposing a manual CLI parameter.

Reporter: David Li / @lidavidm
Assignee: David Li / @lidavidm

PRs and other links:

Note: This issue was originally created as ARROW-13283. Please see the migration documentation for further details.
@asfimport
Copy link
Collaborator Author

yibocai#1:
Maybe also limit #cores.

@asfimport
Copy link
Collaborator Author

Krisztian Szucs / @kszucs:
Issue resolved by pull request 10690
#10690

@asfimport asfimport added this to the 5.0.0 milestone Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lidavidm lidavidm

Labels
Component: Archery Component: Developer Tools Type: enhancement
Projects
None yet
Milestone
5.0.0
Development

No branches or pull requests
2 participants
@lidavidm @asfimport