You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I try to runc, it gave the following error on sh.
sudo ./runc run test
/bin/sh: 0: 3: Invalid argument
Currently I have changed the limits to 10.
"rlimits": [
{
"type": "RLIMIT_NOFILE",
"hard": 10,
"soft": 10
}
],
2 things which I observed:
The moment I changed to hard & soft to 11, things expected to work. Able to enter to the sh shell.
One more observation, the failure happened only for sh, when I change to bash, it works
When the failure happens, I tried via exec command, same error
/bin/sh: 0: 3: Invalid argument
The text was updated successfully, but these errors were encountered:
I presume that it's because sh opens that many files, and so if you limit it enough it won't work? I'm not exactly sure why it gives you an EINVAL rather than EBUSY but this looks to me like it's working as-intended.
When I try to runc, it gave the following error on sh.
sudo ./runc run test
/bin/sh: 0: 3: Invalid argument
Currently I have changed the limits to 10.
"rlimits": [
{
"type": "RLIMIT_NOFILE",
"hard": 10,
"soft": 10
}
],
2 things which I observed:
The moment I changed to hard & soft to 11, things expected to work. Able to enter to the sh shell.
One more observation, the failure happened only for sh, when I change to bash, it works
When the failure happens, I tried via exec command, same error
/bin/sh: 0: 3: Invalid argument
The text was updated successfully, but these errors were encountered: