Every beginning is difficult, but I am already looking forward to the challenges

Incus
, , , ,
1

Hello everyone,

First of all, I would like to wish you all a happy new year and look forward to working with you in 2026…

Well, I’m relatively new here at Linuxcontainers and originally came from the DOCKER scene, which I’m slowly losing interest in :slight_smile:

I would like to become more active in this field in the new year, as I find this software simply brilliant and am more drawn to it.

My project is to have NGINX as a REVERSE proxy locally on the server and run my individual applications under NGINX.

My questions about this would be…

* What is the most sensible way to configure the network for this?

* What is the most sensible storage location for the Docker volume? Standard or something else?

* At home in my LAB network, I also work with VLANa → can I also integrate this for various projects, etc.?

And in general:

Are there already any good books or articles with configuration examples?

Best regards Zhéxué M.

2

I have done that setup. I suggest to create separate containers for each service. There should be a proxy container that is doing the reverse proxy work with nginx. The issue is, how to get external systems to access your reverse proxy?

  1. You can do this with network forwards, How to configure network forwards - Incus documentation
  2. You can do this with proxy devices, Type: proxy - Incus documentation

I would suggest the first option, as it uses firewall rules. The latter uses a separate process that transfers the data between the two networks.