formerly @w3dd1e@lemm.ee

  • 1 Post
  • 4 Comments
Joined 1 year ago
cake
Cake day: June 5th, 2025

help-circle
  • w3dd1e@lemmy.zipOPtoSelfhosted@lemmy.worldCaddy touble in Docker
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 month ago

    It works fine with other ports, including 8443 and 444. It works in Container Station with 443 if I don’t use a Docker Compose file. The whole thing makes no sense.

    I checked to see what was using 443 but all I get is “containerd”. I couldn’t find anymore info on what or why Containerd would be using that and no other containers are running.



  • w3dd1e@lemmy.zipOPtoSelfhosted@lemmy.worldCaddy touble in Docker
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 month ago

    Yeah, I can do that. I just wanted to understand why it work sometimes but not others.

    I HATE QTS. It’s all proprietary software and it’s locked down so I can’t use CLI at all unless I SSH into it. And when I do that, I still can’t add 3rd party software that isn’t in their App Store because there is no apt, dnf, brew, or other similar tools.

    I’ve been considering trying to install TrueNAS or something else on it but it sounds like that will be a hassle too because the fans don’t want to work.


  • w3dd1e@lemmy.zipOPtoSelfhosted@lemmy.worldCaddy touble in Docker
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 month ago

    Yes it works fine if I build the container from The imagine directly inside the container station app, but I’m having trouble pointing that to the Caddyfile.

    If I try to create the container from a docker compose file, it says it can’t bind to port 443 because it’s already in use.