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
documentation for debugging plugins mentions an executable docker-runc as well as a directory /var/run/docker/plugins/runtime-root/moby-plugins which do not exist.
searching around on the internet I found instructions for using runc to find docker plugin container ids and spawning a shell process within plugin containers
instructions state
sudo docker-runc --root /var/run/docker/plugins/runtime-root/moby-plugins list
sudo docker-runc --root /var/run/docker/plugins/runtime-root/moby-plugins exec -t $PLUGID sh
should be
sudo runc --root /run/docker/runtime-runc/plugins.moby list
sudo runc --root /run/docker/runtime-runc/plugins.moby exec -t $PLUGID sh
You can fork the repository, and open a pull request from your fork. All changes in this repository are made through pull requests, so write access is only used for maintainers to merge pull requests, but nobody works directly in this repository.
You can find some docs in the moby repository; https://github.com/moby/moby/tree/master/docs/contributing
Description
documentation for debugging plugins mentions an executable docker-runc as well as a directory /var/run/docker/plugins/runtime-root/moby-plugins which do not exist.
searching around on the internet I found instructions for using runc to find docker plugin container ids and spawning a shell process within plugin containers
instructions state
sudo docker-runc --root /var/run/docker/plugins/runtime-root/moby-plugins list
sudo docker-runc --root /var/run/docker/plugins/runtime-root/moby-plugins exec -t $PLUGID sh
should be
sudo runc --root /run/docker/runtime-runc/plugins.moby list
sudo runc --root /run/docker/runtime-runc/plugins.moby exec -t $PLUGID sh
Reproduce
navigate to and view this webpage https://docs.docker.com/engine/extend/#debugging-plugins
Expected behavior
No response
docker version
docker info
Additional Info
No response
The text was updated successfully, but these errors were encountered: