-
Notifications
You must be signed in to change notification settings - Fork 261
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
Support being able to set CPU/memory limits from the CLI (Docker Desktop) #170
Comments
BTW there is a workaround to edit the settings.json file directly. (This doesn't take away from the feature request to be able to do it on the CLI). |
Thanks @stephen-turner - is there a reference/example of this file somewhere I could use? |
No, it's not documented, but the format is pretty obvious. |
Thanks is there an example file I can look at somewhere? |
You have one on your machine already, so it's just a matter of editing the existing one. Sorry, I don't remember the exact path at the moment as I'm on a Windows machine, but I think you can find it: if not, ask again. |
I don't actually have Docker installed myself, I'm iterating via GitHub Actions. But I found the answer: Thanks again! |
Great, thanks. Your request is actually a specific instance of a class of feature requests we get, so I've made a roadmap item for the general case, #172. I'll close this ticket in favour of that one, but please do vote on that one with a 👍. |
Per @nebuk89 on Slack, raising this as a follow up to docker/for-mac#4907
Tell us about your request
I would like to be able to configure the CPU and memory limits from the CLI (context here is Docker Desktop for Mac)
Which service(s) is this request for?
Docker Desktop (for Mac)
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
When using Docker Desktop for Mac via a CI setup (i.e. headless) environment, it is impossible to set CPU/memory limits.
Are you currently working around the issue?
No, there does not appear to be a workaround as of today.
Additional context
n/a
The text was updated successfully, but these errors were encountered: