• 0 Posts
  • 167 Comments
Joined 2 年前
cake
Cake day: 2023年6月26日

help-circle
  • tux7350toSelfhostedDocker security
    link
    fedilink
    English
    arrow-up
    5
    ·
    9 天前

    Course, feel free to DM if you have questions.

    This is a common setup. Have a firewall block all traffic. Use docker to punch a hole through the firewall and expose only 443 to the reverse proxy. Now any container can be routed through the reverse proxy as long as the container is on the same docker network.

    If you define no network, the containers are put into a default bridge network, use docker inspect to see the container ips.

    Here is an example of how to define a custom docker network called “proxy_net” and statically set each container ip.

    networks:
      proxy_net:
        driver: bridge
        ipam:
          config:
            - subnet: 172.28.0.0/16
    
    services:
      app1:
        image: nginx:latest
        container_name: app1
        networks:
          proxy_net:
            ipv4_address: 172.28.0.10
        ports:
          - "8080:80"
    
      whoami:
        image: containous/whoami:latest
        container_name: whoami
        networks:
          proxy_net:
            ipv4_address: 172.28.0.11
    

    Notice how “who am I” is not exposed at all. The nginx container can now serve the whoami container with the proper config, pointing at 172.28.0.11.


  • tux7350toSelfhostedDocker security
    link
    fedilink
    English
    arrow-up
    7
    ·
    9 天前

    Well if your reverse proxy is also inside of a container, you dont need to expose the port at all. As long as the containers are in the same docker network then they can communicate.

    If your reverse proxy is not inside a docker container, then yes this method would work to prevent clients from connecting to a docker container.


  • tux7350toSelfhostedDocker security
    link
    fedilink
    English
    arrow-up
    13
    ·
    9 天前

    Something like this. This is a compose.yml that only allows ips from the local host 8080 to connect to the container port 80.

    services:
      webapp:
        image: nginx:latest
        container_name: local_nginx
        ports:
          - "127.0.0.1:8080:80"
    


  • You might be thinking of one of the main characters, Edward. Her character has a masculine name but is drawn pretty androgynous, but by all accounts she identifies as a girl. Pretty progressive for the time that it was released. There was also a scene with a posititue in drag.

    I think that scene is in the Cowboy Bebop movie. Edward goes trick or treating and knocks on the door of a prostitute in drag. The prostitute then confuses Edward for being a little boy and gets mad saying when they realize Edward is a girl.









  • tux7350to196@lemmy.blahaj.zoneBittorrule
    link
    fedilink
    English
    arrow-up
    2
    ·
    3 个月前

    Got ya, thanks for the reply! Ive got 2x8tb for 16tb total and thats worked for me for years. The drives are getting old and I’ve been worried about the data. Checking out other drives but it would be nice to just… not deal with hardware. Is there any upload / download rates?



  • tux7350toTechnology*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    2
    ·
    3 个月前

    Hmm these are some pretty cool features I’d be interested in. I currently use Voyager for lemmy and quite like the layout. Does Piefed have any good mobile clients? Is there something you’d recommend?