Unable to exec into container after re-adding a scope rule

criblio / appscope

Gain observability into any Linux command or application with no code modification

https://appscope.dev

Apache License 2.0

268 stars 33 forks source link

Unable to exec into container after re-adding a scope rule #1597

Closed seanvaleo closed 1 year ago

seanvaleo commented 1 year ago

Reproduction steps:

add a scope rule
start a new container

remove the rule, (save), re-add it, (save)

docker exec -it ubuntu-2 ls
OCI runtime exec failed: exec failed: unable to start container process: open /dev/ptmx: no such file or directory: unknown

docker exec -it ubuntu-2 /bin/bash
OCI runtime exec failed: exec failed: unable to start container process: open /dev/ptmx: no such file or directory: unknown

seanvaleo commented 1 year ago

It's highly possible that we are configuring the container as a "new container" , then configuring the container as an "existing container", which would result in duplicate mounts etc.

seanvaleo commented 1 year ago

We intend to resolve this by preventing mounts from being added when they already exist

seanvaleo commented 1 year ago

We have been unable to reproduce this ; and have proven that duplicate mounts were not the cause of the issue. Closing.