-
Notifications
You must be signed in to change notification settings - Fork 125
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
unmarshal failed when set ulimit with -1 #154
Comments
It's trying to convert to a |
Trying setting it to "-1" fails on docker-compose. $ docker-compose up
ERROR: Validation failed in file './docker-compose.yml', reason(s):
services.app.ulimits.memlock contains an invalid type, it should be an integer, or an object Also fails without docker-compose. option "-1" converts to $ docker run -d --ulimit memlock=-1 --name app ehazlett/docker-demo
1db141cac32f382304210d9107d97146c709e0f43321052eb4fa710ec7bedf17
$ docker inspect app | grep Ulimit -A 5
"Ulimits": [
{
"Name": "memlock",
"Hard": -1,
"Soft": -1
} I think it may be a bug for samalba/dockerclient, because the types defined between dockerclient and docker/go-unit are different.
So I issued this problem to dockerclient, too. samalba/dockerclient#239 |
Internally we should move to the official Docker Go library (docker/engine-api). That should fix these. |
I got it. Thank you for kindly reply. |
This works: (very simliar to Swarm Example)
But when setting ulimit to -1 (-1 means
unlimited
and there is no way to set tounlimited
), interlock fails.I think interlock does not handle the value
-1
(which meansunlimited
), and I hope interlock handles it.I attached my environment and container which make fail.
Thank you.
The text was updated successfully, but these errors were encountered: