Skip to content

Rootless: do not always run environment-to-ini which causes issues with read-only file setups (swarm, k8s, etc.) #15719

Closed
@decentral1se

Description

@decentral1se
  • Gitea version (or commit ref): Latest rootless release
  • Git version: Latest release on Debian 10
  • Operating system:
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
  • Log gist:

Description

Following #14762.

Thanks for this work but this needs to be made optional. When deploying Gitea using docker swarm, you pass the app.ini as a read-only file. Then when environment-to-ini is always run, the deployment fails because it cannot edit that file. Ideally, there would be an environment var that you could set to avoid running this command. For now, I have to override the entrypoint.

Something conditional to be wrapped around:

environment-to-ini --config ${GITEA_APP_INI}

And #14762 (comment).

Screenshots

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions