this post was submitted on 18 Nov 2026
53 points (100.0% liked)

Selfhosted

63973 readers
1847 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

I've been trying to figure this part out for a few days. I have my own Forgejo instance and a website each running in separate containers on a Raspberry Pi. I also have the forgejo runner installed in another docker container. I followed some guides to set up forgejo actions, but all the guides end with a simple example that basically just runs the "ls" command.

I tried running 'docker compose up' inside my workflow, but it fails with "docker: command not found". So how do you use the workflow to actually update the website in the other container?

I think I'd prefer keeping everything in docker but I'd be okay with making the workflow run some script on the host machine if needed.

you are viewing a single comment's thread
view the rest of the comments
[–] tofu@lemmy.nocturnal.garden 5 points 3 days ago

The error comes from the fact that you run the forgejo runner with an image that doesn't have Docker, you'd need docker-in-docker (dind) in that case. But to update the homepage, you need to run docker on the host where it is.

There's 2 common ways to achieve what you want.

  1. on the website host, run an agent that checks out the git repo in intervals (or gets triggered by a forgejo webhook) and deploys it there. A common solution for that is Komodo, but there's others as well. You don't need the forgejo runner in this scenario, at least not for the deployment, everything is managed by Komodo.

  2. in the forgejo runner, you run a script that sshs into the website host and runs docker there, checking out the remote repo and deploys it with docker. A common tool for this is Ansible, which has modules for a lot of cases so you don't need to cobble together an ugly bash script