Skip to content

Plugins should always run in a read-only filesystem #17

Description

@byrongamatos

Restored from slopsmith/slopsmith#120 — original issue, opened by @mogul on 2026-05-01.
[restored-from: slopsmith/slopsmith#120]

I spent a lot of time making PRs to fix things that wanted to write to areas that are intended to be static and read-only in a .AppImage. People iterating on slopsmith and plugins were not aware this was a problem. To eliminate this entire class of bug, Docker instructions should mount code and static assets via a read-only volume mount so everyone sees the problem when the code is written.

Metadata

Metadata

Assignees

No one assigned

    Labels

    cap:2:backend-routesPlugin or server route behaviorcap:7:pipelineCapability graph registration, dispatch, claims, ownership, and compatibility shimspluginRelates to a slopsmith plugin

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions