cmd/create, cmd/initContainer: Mount the devpts file system at runtime #1257
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Anything that's specified during
podman create ...
gets staticallybaked into the container's configuration, and is either difficult or
impossible to change afterwards. This means that Toolbx containers
created with older versions of Toolbx keep diverging from those created
with newer versions. Hence, making it complicated to keep older
containers working with newer Toolbx.
Mounting the
devpts
file system at runtime as part of the Toolbxcontainer's entry point will make it possible to update the attributes
of the mount, if necessary, for both existing and newly created
containers.
For what it's worth, this does alter the mount options by removing
context
.With
podman create --mount type=devpts,destination=/dev/pts
it was:Now with
mount -t devpts -o noexec,nosuid,gid=5,mode=620,ptmxmode=666
it is:
#1016