Skip to content

Non root container #93

Open
Open
@Southclaws

Description

@Southclaws

The Pico Docker image is currently root (the insane default of Docker)

This means that making quick ad-hoc changes to targets or config is quite annoying. You have to chown the targets directory, do your quick changes/tests and chown it back to root (or let Pico overwrite with root).

Instead, there should be a better solution to this, allowing users to deploy new setups easily where they can deploy manually a few times to work out any first-time-deploy issues then commit those changes and leave Pico to handle the rest.

The ideal workflow would be:

  • Add a target to Pico, with a no-op up command
  • Pico clones this to its targets directory
  • You jump in and do your own docker-compose up and figure out any last-minute deployment details you need
  • Once you're happy with the setup and the target is running, change the up command to the live version
  • Pico takes over
  • At any point you can jump in and make ad-hoc changes to the live target then commit your changes

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions