I have a few seperate docker compose files and I thought to make my life easier, I’d just include them in another file and that should work like the project manager. But it keeps trying to take ownership. Is there anyway to avoid that so they’re all treated as separate autonomous docker files?

  • HelloRoot
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    22 days ago

    My bad I misread. I don’t think you can include multiple compose files into one in a clean way.


    There are profiles which you could look into but I am not sure whether that would work like you want.

    services:
      app1:
        profiles: ["project1"]
        ...
    
      app2:
        profiles: ["project2"]
        ...
    
    docker compose --profile project1 up
    

    Personally I use dokploy, but thats a whole big ass project. It can manage multiple compose files (among many other features). https://github.com/Dokploy/dokploy

    Maybe look for a more minimal alternative. Like https://github.com/beanworks/dcm

    Actually I just remembered hearing good things about https://github.com/louislam/dockge