Skip to content

portable service with read-only image and trusted profile has no writable /tmp #23592

Description

@AlbanBedel

systemd version the issue has been seen with

247.6

Expected behaviour you didn't see

Portable services should always have a writable /tmp

Unexpected behaviour you saw

/tmp is not writable with the trusted profile and a read-only image

Steps to reproduce the problem

Create a squashfs image that need to write to /tmp and start it with the trusted profile.

All profiles except trusted have DynamicUser=yes set, which imply PrivateTmp=yes, as a result the portable service always have a writable /tmp, even with a read only image. There is no such option in the trusted profile, so if the image is read-only /tmp is not writable by default.

Even if the image is writable we probably don't want writes to /tmp to modify the image, so it should either use the host /tmp or its own tmpfs.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    RFE 🎁Request for Enhancement, i.e. a feature requestportableAnything to do with systemd-portable and portablectl and portables

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions