this post was submitted on 10 Dec 2025
15 points (89.5% liked)

Selfhosted

53668 readers
592 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
15
How to integrate user-compiled docker services with Dockge? (sopuli.xyz)
submitted 6 days ago by enchantedgoldapple@sopuli.xyz to c/selfhosted@lemmy.world
5 comments fedilink hide all child comments
 

There are a few Docker projects I haven't been able to properly implement in my homelab, only because their images need to be user-compiled and Dockge doesn't seem to have an option to include the entire repository required for the project compilation in its interface or in the stacks directory. I know I could just host them in a separate directory but I would like my services to be manageable from a single place and following this approach isolates the service from being controlled from Dockge.

Is there some workaround or a solution for this I am unaware of? I initially thought I could deploy Coolify within Dockge and store the applications under it but apparently Coolify is meant to work on its own and I fear running both Coolify and Dockge will break stuff.

you are viewing a single comment's thread
view the rest of the comments
[–] darkan15@lemmy.world 2 points 6 days ago

As far as I know, Dockge, Portainer, Coolify, etc. can have different stacks folders, and they will not show, warn you or not let you manage stacks outside their designated paths.

For your main question, it is possible to build your image on the same system, you would need at least terminal access to do so, and then use the local image with docker compose or Dockge or other, you just would need to reference its image name instead of a URL (to differentiate images I build I prefix their name with local as 'local/service-name'), and it would not pull from anywhere but use the one you already built, you could do it on any folder on the system or inside the stacks folder you have with Dockge

If you do it on Dockge's stack folder, create a folder for your service, with a docker-compose.yml file inside (with just this it will appear in Dockge), then pull the repository on this folder, and make sure you have the proper Dockerfile to build the image, you can then either build the image first or reference the Dockerfile on your docker-compose.yml. This way when you do docker compose up or in Dockge you press the Start button, it will build the image with the Dockerfile and use it, if it doesn't find the image.

The other option I know is to have a local image registry (I have done this with Forgejo), so pull the repository on any folder on your system, build it and push it to your local registry, and then just use the local registry URL on your docker-compose-yml