-
Notifications
You must be signed in to change notification settings - Fork 645
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
docker:start : ulimit option not configurable #484
Comments
You are right, this is currently not supported but would be a nice addition. If you feel fancy, PRs are always welcome ;-) If not no problem, we can implement it in a later release. Just in case, let me know whether you are interested, I could give you the proper pointers (it's an easy one). |
Hi, Yes i'd like to contribute a PR on this subject 2016-06-28 17:07 GMT+02:00 Roland Huß [email protected]:
|
Great ! You'd best start at RunImageConfiguration which holds the configuration for At the end it should be possible to specify ulimits within <run>
<ulimits>
<ulimit>
<name>memlock</name>
<hard>-1</hard>
<soft>-1</soft>
</ulimit>
....
</ulimits>
....
</run> At lease one of When you are doing the PR, it would be awesome if you could
Don't hesitate to ask, if something is not clear ;-) Thanks again, we love pull requests ;-) |
Hello, |
* Formatted documentation * Added some more mtests * Added to sample project some ulimits * Removed builder in favor of direct instantiation * Renamed "ULimit" to "Ulimit" This relates to the PR #507.
Thanks a lot ! It will be available in the next release. |
Hello,
In order to start my container, i have to set the option "--ulimit" in the command line :
"docker run --ulimit memlock=-1:-1 ....."
I checked the docker-maven-plugin documentation and the source code, but didn't see anything related to this.
It would be nice if plugin can manage this.
The text was updated successfully, but these errors were encountered: