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

[seanvaleo]

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]

maybe related: docker/cli#2067

[seanvaleo]

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]

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

[seanvaleo]

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