Hi guys! I’m going at my first docker attempt…and I’m going in Proxmox. I created an LXC container, from which I installed docker, and portainer. Portainer seems happy to work, and shows its admin page on port 9443 correctly. I tried next running the image of immich, following the steps detailed in their own guide. This…doesn’t seem to open the admin website on port 2283. But then again, it seems to run in its own docker internal network (172.16.0.x). How should I reach immich admin page from another computer in the same network? I’m new to Docker, so I’m not sure how are images supposed to communicate within the normal computer network…Thanks!

  • Avid Amoeba@lemmy.ca
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    4
    ·
    edit-2
    3 months ago

    Did you say you’re running docker in LXC? So container in a container? If yes, that’s generally an anti pattern.

  • Kaavi@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    3 months ago

    I’ve been using proxmox mainly with lxc containers for years. I gave an lxc running docker and portainer, for a few services I have running in docker.

    I wouldn’t do it with anything critical it anything that needs mich performance or resources. But honestly most things don’t need that.

    So is you like me just need a few docker containers and you already have everything else running - this can be a fine way to do it. Go for it :)

  • Decronym@lemmy.decronym.xyzB
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    3 months ago

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

    Fewer Letters More Letters
    HA Home Assistant automation software
    ~ High Availability
    HTTP Hypertext Transfer Protocol, the Web
    IP Internet Protocol
    LXC Linux Containers
    NAS Network-Attached Storage
    NFS Network File System, a Unix-based file-sharing protocol known for performance and efficiency
    nginx Popular HTTP server

    6 acronyms in this thread; the most compressed thread commented on today has 6 acronyms.

    [Thread #664 for this sub, first seen 8th Apr 2024, 10:55] [FAQ] [Full list] [Contact] [Source code]

  • N0x0n@lemmy.ml
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    3 months ago

    Docker networking is fun :) (IMO).

    Without having a look at your container and how you configured it, if you have correctly mapped your ports and didn’t change anything fancy and don’t use a reverse proxy

    Your container should be accessible on your host’s IP mapped with you Immich docker port:

    HostIP:2283

    Edit: Also, don’t run a docker container in… Another container (LXC).

    Containerinception

    • iturnedintoanewt@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 months ago

      Thanks! When I type my LXC’s IP:2283, I get unable to connect. I checked the docker-compose.yml and the port seems to be 2283:3001, but no luck at either. Is there anything that needs to be done on docker’s network in order to…“publish” a container to the local network so it can be seen? Or any docker running with a port can be reached via the host’s IP with no further config? Checking the portainer’s networks section, I can see an ‘immich-default’ network using bridge on 172.18.0.0/16, while the system’s bridge seems to be running at 172.17.0.0/16. Is this the correct defaults? Should I change anything?

      Thanks!

      • WhyAUsername_1@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 months ago

        Can you reach other services on that vm? If you don’t know that then test this first. ( May be run a python http service to test this?)