coop-cloud/mastodon
1
0
Fork 3
generated from coop-cloud/example
Code Issues 11 Pull Requests 7 Projects Releases Wiki Activity

fix: run Mastodon app as mastodon user with character limit override #64

Open
ChasquiLabo wants to merge 1 commits from escuela-comun/mastodon:fix/character-limit-run-as-mastodon into main
pull from: escuela-comun/mastodon:fix/character-limit-run-as-mastodon
merge into: :main
Conversation 0 Commits 1 Files Changed 1
+1 -1
ChasquiLabo commented 2026-09-29 18:31:10 +00:00
First-time contributor
Copy Link
Copy Source

The issue comes from compose.character-limit.yml.

The app service needs to start as root in order to apply the sed
changes for the custom character limit. However, the current command:

su -c "RAILS_ENV=production bundle exec rails s -p 3000"

also leaves Rails/Puma running as root.
As a result, uploaded media files can be created as root:root, while
Sidekiq runs as the mastodon user (991:991). This causes video
post-processing to fail because Sidekiq cannot correctly process some
of the generated media files.
This changes the final command to:

exec su -s /bin/sh -c \
  "RAILS_ENV=production bundle exec rails s -p 3000" \
  mastodon

The container can still perform the initial setup as root, but
Rails/Puma then runs as mastodon.
Tested on a real Co-op Cloud Mastodon deployment with Mastodon 4.5.18.
After the change:

  • Rails/Puma runs as mastodon
  • media files are created with compatible ownership
  • Sidekiq can process uploaded videos correctly
  • video uploads work again

Related to #63.
Fix made with LLM Chatgpt

The issue comes from `compose.character-limit.yml`. The `app` service needs to start as `root` in order to apply the `sed` changes for the custom character limit. However, the current command: ```sh su -c "RAILS_ENV=production bundle exec rails s -p 3000" ``` also leaves Rails/Puma running as root. As a result, uploaded media files can be created as root:root, while Sidekiq runs as the mastodon user (991:991). This causes video post-processing to fail because Sidekiq cannot correctly process some of the generated media files. This changes the final command to: ```sh exec su -s /bin/sh -c \ "RAILS_ENV=production bundle exec rails s -p 3000" \ mastodon ``` The container can still perform the initial setup as root, but Rails/Puma then runs as mastodon. Tested on a real Co-op Cloud Mastodon deployment with Mastodon 4.5.18. After the change: - Rails/Puma runs as mastodon - media files are created with compatible ownership - Sidekiq can process uploaded videos correctly - video uploads work again Related to #63. Fix made with LLM Chatgpt
ChasquiLabo added 1 commit 2026-09-29 18:31:10 +00:00
fix: run Mastodon app as mastodon user with character limit override
continuous-integration/drone/pr Build is failing
Details
9823a22e55
Some required checks failed
continuous-integration/drone/pr Build is failing
Details
You are not authorized to merge this pull request.
This pull request can be merged automatically.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u https://git.coopcloud.tech/escuela-comun/mastodon fix/character-limit-run-as-mastodon:escuela-comun-fix/character-limit-run-as-mastodon
git checkout escuela-comun-fix/character-limit-run-as-mastodon
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
3wordchant aadil (Aadil Ayub) abra-bot (Abra Bot) ammaratef45 amras (Sarma) benjaminlyng (Benjamin Lyng Jørgensen) BornDeleuze Brooke cas (Cassowary) coopcloud decentral1se (d1) fauno (fauno) jjsfunhouse kawaiipunk (KawaiiPunk) knoflook moosemower moritz nicksellen (Nick Sellen) notplants oxaliq (sorrel) p4u1 renovate-bot (Comrade Renovate Bot) simon stevensting trav (Trav Fryer) yksflip
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/mastodon#64