You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2021/02/05 21:01:16 UTC

[GitHub] [openwhisk] hykych opened a new issue #3711: How do you use docker-runc in a container?

hykych opened a new issue #3711:
URL: https://github.com/apache/openwhisk/issues/3711


   I mount  `/usr/bin/docker-runc` and `/run/runc` to a container.
   when I use command `docker-runc list` in the container, I got this.
   ```
   2a1391bec47e97c960180ecd0fe4fa8bdad06f3a966a4ab56a185fea46012897   0           stopped     /run/docker/libcontainerd/2a1391bec47e97c960180ecd0fe4fa8bdad06f3a966a4ab56a185fea46012897   2018-04-23T11:49:09.45250519Z    root
   936ade0c1f01c5b47949d57af420738149f6b57854ee5a56da70b7c2d869cde4   0           stopped     /run/docker/libcontainerd/936ade0c1f01c5b47949d57af420738149f6b57854ee5a56da70b7c2d869cde4   2018-04-23T11:49:09.829041553Z   root
   93beb0d83e18b9eae82b9bfd2a26f4ee9811f652a9b43650141741d9934f9e83   0           stopped     /run/docker/libcontainerd/93beb0d83e18b9eae82b9bfd2a26f4ee9811f652a9b43650141741d9934f9e83   2018-05-29T09:26:50.29931867Z    root
   972876048d960149e11c5519f347e3b24d8e889810a4d3f061e4f898e58c38ad   0           stopped     /run/docker/libcontainerd/972876048d960149e11c5519f347e3b24d8e889810a4d3f061e4f898e58c38ad   2018-05-29T09:26:49.771647667Z   root
   b42cea49135de0e91d5968941e372a985a416c380b4059b5a0ac9d3259ca24b0   0           stopped     /run/docker/libcontainerd/b42cea49135de0e91d5968941e372a985a416c380b4059b5a0ac9d3259ca24b0   2018-04-23T11:49:08.731506397Z   root
   c63133e715961bdbea6048c7d1659b8fd4e5b4119630b19df08591728f7d15a3   0           stopped     /run/docker/libcontainerd/c63133e715961bdbea6048c7d1659b8fd4e5b4119630b19df08591728f7d15a3   2018-04-23T11:49:09.239295667Z   root
   e68f86337e88c9e5eba7d66e9f4bcf48bfaabfb5827f6484536389b0fd6214ed   0           stopped     /run/docker/libcontainerd/e68f86337e88c9e5eba7d66e9f4bcf48bfaabfb5827f6484536389b0fd6214ed   2018-04-23T11:49:08.927237725Z   root
   ```
   
   it seems like I can't get the correct status of the containers, and I got this when I use `docker-runc pause`
   ```
   container not running or created: stopped
   ```
   
   How do you solve this problem?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [openwhisk] hykych commented on issue #3711: How do you use docker-runc in a container?

Posted by GitBox <gi...@apache.org>.
hykych commented on issue #3711:
URL: https://github.com/apache/openwhisk/issues/3711#issuecomment-781794717


   @dgrove-oss The reason why I ask about how to use runc is I found that at sometime docker hangs(does not respond) for more than 10 seconds if operate docker too often.
   I don't know if you guys encountered such a problem.  It's highly possible that contained's GC cause it(docker hangs) and docker doesn't expose the parameter to tune the containerd's GC.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [openwhisk] rabbah commented on issue #3711: How do you use docker-runc in a container?

Posted by GitBox <gi...@apache.org>.
rabbah commented on issue #3711:
URL: https://github.com/apache/openwhisk/issues/3711#issuecomment-801164587


   The reason for this is that the invoker PID is not the same as the post. For Kubernetes, you can fix this by adding
   ```yaml
        hostPID: true
   ```
   to your pod spec.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [openwhisk] dgrove-oss edited a comment on issue #3711: How do you use docker-runc in a container?

Posted by GitBox <gi...@apache.org>.
dgrove-oss edited a comment on issue #3711:
URL: https://github.com/apache/openwhisk/issues/3711#issuecomment-774304573


   Recalling from several years ago, but I think you need to have an almost perfect match of docker version on the host machine and in the invoker container.  Otherwise when the invoker uses its `runc` to try talk to the host `runc` via the mounted socket, you get grpc version mismatch and it doesn't work.
   
   The workaround is just don't use runc....fallback to using docker pause/unpause.  The performance gain from using runc was pretty important before the pause grace period was introduced.  Waiting 50ms before pausing usually pushes the pause/unpause frequency down a fair amount, so the few ms you save from runc vs. docker pause has less impact.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [openwhisk] bdoyle0182 commented on issue #3711: How do you use docker-runc in a container?

Posted by GitBox <gi...@apache.org>.
bdoyle0182 commented on issue #3711:
URL: https://github.com/apache/openwhisk/issues/3711#issuecomment-774286316


   I'd like to reopen this issue so we can solve and document how to work around this. I'm guessing it has something to do with some host level or docker server configuration. This seems to be the exact issue I'm facing @style95 and after discussing with my team it seems to be independent of the docker upgrade in 2019. 


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [openwhisk] dgrove-oss commented on issue #3711: How do you use docker-runc in a container?

Posted by GitBox <gi...@apache.org>.
dgrove-oss commented on issue #3711:
URL: https://github.com/apache/openwhisk/issues/3711#issuecomment-774304573


   Recalling from several years ago, but I think you need to have an almost perfect match of docker version on the host machine and in the invoker container.  Otherwise when the invoker tries to talk to runc, you get grpc version mismatch and it doesn't work.
   
   The workaround is just don't use runc....fallback to using docker pause/unpause.  The performance gain from using runc was pretty important before the pause grace period was introduced.  Waiting 50ms before pausing usually pushes the pause/unpause frequency down a fair amount, so the few ms you save from runc vs. docker pause has less impact.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org