this post was submitted on 17 Mar 2024
54 points (82.1% liked)

Selfhosted

40347 readers
325 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.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
54
Docker - what use is it? (sh.itjust.works)
submitted 8 months ago by Amongussussyballs100@sh.itjust.works to c/selfhosted@lemmy.world
42 comments fedilink hide all child comments
 

I see Docker mentioned every other thread and was wondering how useful it is for non development things, and if so what they are.

you are viewing a single comment's thread
view the rest of the comments
[–] JoeCoT@fedia.io 9 points 8 months ago (3 children)

So it's always going to be used for technical things, but not necessarily development things. I use it for both.

For my home server setup I have docker setup like this:

  1. A VPN docker container
  2. A transmission (bittorrent client) container, using the VPN's network
  3. An nginx (web server) container, which provides access to the transmission container
  4. A 3proxy socks proxy container, using the VPN's network
  5. A tor client container
  6. A 3proxy socks proxy container, using the tor container's network

Usually it's pretty hard to say "these specific programs and only these should run over my VPN". Docker makes that easy. I can just attach containers to the same network as my VPN container, and their traffic will all go over the VPN. And then with my socks proxies I can selectively put my browser traffic over either the VPN or Tor, using extensions like FoxyProxy. I watch wrestling through my vpn because it's cheaper overseas and has better streaming options, so I have those specific sites set to route through my VPN socks proxy. And I have all onion links set to go through my Tor proxy.

[–] Amongussussyballs100@sh.itjust.works 3 points 8 months ago (2 children)

This looks like an interesting project. Can the vpn container only route traffic that are in other containers, or can regular applications get their traffic routed by the vpn container too?

[–] clmbmb@lemmy.dbzer0.com 1 points 8 months ago* (last edited 8 months ago)

The answer is yes in both cases.

  1. Docker has an internal networking setup. You can create a "network" and all containers in that network communicate with each other, but not with other containers in other networks. So you can set up a VPN container in a network and all containers in that netowrk could use the VPN to route their traffic through.
  2. You can configure your VPN container to expose some ports that it uses to communicate, and then the "regular applications" can make use of those ports to connect through the VPN.
load more comments (1 replies)
load more comments (1 replies)