Is it possible to specify environment variables instead of using a .env file? Looking to add a portainer template for it via: SelfhostedPro/selfhosted_templates#97

I've followed the instructions on a freshly spun up ubuntu lxc on my proxmox box, inside with the latest docker attempting to start the lancache container fails with the following error:

root@docker:~/lancache# docker-compose up -d ERROR: The Compose file './docker-compose.yml' is invalid because: services.dns.ports contains an invalid type, it should be a number, or an object services.dns.ports contains an invalid type, it should be a number, or an object

The documentation at https://lancache.net/docs/containers/dns/variables/ states:

UPSTREAM_DNS
The upstream DNS server(s) the cache should use. The defaults are Google DNS. Multiple upstream dns servers are allowed, separated by semi colons (or spaces). Do NOT point this at lancache-dns.

However, with this configured:

UPSTREAM_DNS=1.1.1.1 8.8.8.8 149.112.121.10 8.8.4.4

this error results:

dns_1         | /etc/bind/named.conf.options:15: missing ';' before '8.8.8.8'
dns_1         | /etc/bind/named.conf.options:15: missing ';' before '149.112.121.10'
dns_1         | /etc/bind/named.conf.options:15: missing ';' before '8.8.4.4'

Changing UPSTREAM_DNS to use semicolons starts the container just fine.

UPSTREAM_DNS=1.1.1.1; 8.8.8.8; 149.112.121.10; 8.8.4.4

Hope this helps

Example: using fe80::d as a local subnet IPv6 DNS address...

services.dns.ports is invalid: Invalid port ":53:53/tcp", should be [[remote_ip:]remote_port[-remote_port]:]port[/protocol]

https://docs.docker.com/compose/compose-file/compose-file-v3/ support does exist; otherwise, port-forwarding could be set up via haproxy or other UDP/TCP dual-stack port forwarding software.

Thanks for making this!

Some games work as expected, 7 days to die is one of them.
However, a few that I have tested stop downloading all together. Checking steam's content_log shows that the chunks are coming in with crc errors.
Games with issues that I have tested: Fallout 4 & Ark Survival Evolved

Some output of the steam content_log file.
[2020-04-25 10:46:21] HTTP (SteamCache,20) - cache8-atl1.steamcontent.com (172.16.8.20:80 / 172.16.8.20:80, host: cache8-atl1.steamcontent.com): Closing connection [2020-04-25 10:46:21] Created download interface of type 'SteamCache' (7) to host cache7-lax1.steamcontent.com (cache7-lax1.steamcontent.com) [2020-04-25 10:46:21] HTTP (SteamCache,302) - cache11-atl1.steamcontent.com (172.16.8.20:80 / 172.16.8.20:80, host: cache11-atl1.steamcontent.com): CRC check failed for chunk /depot/377161/chunk/8f8692f4a6d765811f5dbd9425d1702f9bdf0f01 - converting to 404 [2020-04-25 10:46:21] HTTP (SteamCache,302) - cache11-atl1.steamcontent.com (172.16.8.20:80 / 172.16.8.20:80, host: cache11-atl1.steamcontent.com): Received 404 (Not Found) HTTP response for depot 377161 [2020-04-25 10:46:21] HTTP (SteamCache,55) - cache17-lax1.steamcontent.com (172.16.8.20:80 / 172.16.8.20:80, host: cache17-lax1.steamcontent.com): CRC check failed for chunk /depot/377161/chunk/2b2ac893e60bb23d62be8775a0a5dccf9a8e7b44 - converting to 404 [2020-04-25 10:46:21] HTTP (SteamCache,55) - cache17-lax1.steamcontent.com (172.16.8.20:80 / 172.16.8.20:80, host: cache17-lax1.steamcontent.com): Received 404 (Not Found) HTTP response for depot 377161 [2020-04-25 10:46:21] HTTP (SteamCache,302) - cache11-atl1.steamcontent.com (172.16.8.20:80 / 172.16.8.20:80, host: cache11-atl1.steamcontent.com): Closing connection [2020-04-25 10:46:21] Created download interface of type 'SteamCache' (7) to host cache21-lax1.steamcontent.com (cache21-lax1.steamcontent.com) [2020-04-25 10:46:21] HTTP (SteamCache,125) - cache7-lax1.steamcontent.com (172.16.8.20:80 / 172.16.8.20:80, host: cache7-lax1.steamcontent.com): CRC check failed for chunk /depot/377161/chunk/912044ed53081808cb7b52cfd91560dfd66fdddf - converting to 404 [2020-04-25 10:46:21] HTTP (SteamCache,125) - cache7-lax1.steamcontent.com (172.16.8.20:80 / 172.16.8.20:80, host: cache7-lax1.steamcontent.com): Received 404 (Not Found) HTTP response for depot 377161 [2020-04-25 10:46:21] HTTP (SteamCache,55) - cache17-lax1.steamcontent.com (172.16.8.20:80 / 172.16.8.20:80, host: cache17-lax1.steamcontent.com): CRC check failed for chunk /depot/377161/chunk/8f8692f4a6d765811f5dbd9425d1702f9bdf0f01 - converting to 404 [2020-04-25 10:46:21] HTTP (SteamCache,55) - cache17-lax1.steamcontent.com (172.16.8.20:80 / 172.16.8.20:80, host: cache17-lax1.steamcontent.com): Received 404 (Not Found) HTTP response for depot 377161 [2020-04-25 10:46:21] HTTP (SteamCache,59) - cache21-lax1.steamcontent.com (172.16.8.20:80 / 172.16.8.20:80, host: cache21-lax1.steamcontent.com): CRC check failed for chunk /depot/377161/chunk/2b2ac893e60bb23d62be8775a0a5dccf9a8e7b44 - converting to 404 [2020-04-25 10:46:21] HTTP (SteamCache,59) - cache21-lax1.steamcontent.com (172.16.8.20:80 / 172.16.8.20:80, host: cache21-lax1.steamcontent.com): Received 404 (Not Found) HTTP response for depot 377161

Hi,
First of all, thanks for this awesome project!
I've been using Lancache at home for the past 1-2 years now as well as on our small friend groups lan party (~40-50 people).

Now I just noticed on my home instance, that the /logs/access.log does not appear to have retention. I was wondering why I ran out of disk space all the sudden, as I have 1.4T disk, I use 1350G for cache and 500M for index, so there should've been ~48G free space for the OS etc.
I just cleared all the caches, but right after that I noticed this:

root@lancache:/cache/logs# ls -la
total 113190328
drwxr-xr-x 2 root root         4096 Jul 27 20:51 .
drwxr-xr-x 4 root root         4096 Jul 27 20:51 ..
-rw-r--r-- 1 root root 115905572629 Jan  2 18:06 access.log
-rw-r--r-- 1 root root       226523 Jan  2 17:53 error.log
-rw-r--r-- 1 root root       651463 Jan  2 17:58 stream-access.log
-rw-r--r-- 1 root root       200704 Dec 23 16:26 stream-error.log
-rw-r--r-- 1 root root        75732 Dec  6 18:12 upstream-error.log

root@lancache:/cache/logs# ls -lah 
total 108G
drwxr-xr-x 2 root root 4.0K Jul 27 20:51 .
drwxr-xr-x 4 root root 4.0K Jul 27 20:51 ..
-rw-r--r-- 1 root root 108G Jan  2 17:54 access.log
-rw-r--r-- 1 root root 222K Jan  2 17:53 error.log
-rw-r--r-- 1 root root 636K Dec 23 16:26 stream-access.log
-rw-r--r-- 1 root root 196K Dec 23 16:26 stream-error.log
-rw-r--r-- 1 root root  74K Dec  6 18:12 upstream-error.log

That's quite big access.log file there 😅 Some kind of retention, for either e.g. 10G or past 30 days or something would be better, imho.

In case you're interested, here's my repo with configs that I use: https://github.com/kirbo/lancache

I just implemented lancache on my home network. The largest problem was that my game machine just would not use the cache server IP for most of the domains (the weird bit was that some of the domains would work, so it was off-and-on).

Tried many things but the real issue was my antivirus.

There is a component of Avast called "Real Site" which is designed to prevent DNS poisoning. Since that is exactly what we're trying to do, this component must be turned off for it to work.

The documentation does mention DNS poisoning, but I think it would be a good idea to call out in the "Common Issues" part of the guide that this is an issue if you have antivirus software and to check it if there are problems. Some screenshots of common types of antivirus software and where to turn this off (like the router DNS guide that you already have) would be very helpful.

Some screenshots:
Litmus test with Real Site turned on:

Litmus test with Real Site turned off (Flush DNS cache and restart browser first):

Turning off Real Site

Real Site turned off:

Real Site turned on:

Real Site location within Avast:

Hi, I was trying to run lancachenet on raspberry using docker, but if i try to create a container with lancachenet/monolithic:latest image, give me error.
The try it to run in a virtual machine and works good.
I'm thinking that the problem is because of the operating system

and some info about docker

is there anything you guys can do, to change the image to work on raspberry

First of all: I don't know if this is the right repo for this issue, if I should post it somewhere else just tell me.
Posted the same issue here

Describe the issue you are having

Starting the docker container(s) via "docker-compose up -d" fails (error message below). As far as I can tell its because something related to access rights.

How are you running the container(s)

Virtualized in an LXC via Proxmox with current docker/docker-compose versions (aka fresh install as of today).
Using this .env file and starting with "docker-compose up -d".
Commands are executed as root (as it is a LXC and that's its only purpose)

DNS Configuration

Irrelevant/Not the issue here.

Output of container(s)

See this pastebin

I can provide further information/logs as needed. Just tell me.

TIA for any help.

Introduction to the problem

As HTX-LAN has been using this awesome piece of software for some years now,
we wanted some more insights into how the cache was utilized live under the LAN parties.

The provided logs did show some HIT and MISS but the actual throughput and performance of the tools were invisible.

Idea

We wanted to export metrics from Bind (DNS) and NGINX in a form that where easy to use in Grafana through Prometheus

Solution

To implement this, we have updated the infrastructure in three services (repositories).

lancache-dns

The first repository, that we have updated, is the lancache-dns.
Here we have added statistics logging to the bind configuration file, which is exposed on port 8053 (TCP).

The core Bind functionality is not changed, but due to statistics now being logged, it does create some extra load. This load is very limited in scope.

This endpoint is not intended to be exposed publicly, but to be used by an exporter, which we have included in the docker-compose repository.

monolithic

The second repository, that we have updated, is the monolithic.
Here we have added a NGINX status endpoint, that returns the current status for NGINX used in the monolithic setup.
This status endpoint is set up as a standalone site configuration (30_metrics.conf).

Through this site configuration, we expose the status endpoint on port 8080 (TCP), with the help of the stub_status functionality in NGINX. By doing it on a standalone site, the endpoint can easily be disabled by not opening the port in the container.

This endpoint is not intended to be exposed publicly, but to be used by an exporter, which we have included in the docker-compose repository.

docker-compose

The third repository, that we have updated, is the docker-compose, which is the repository in which this issue is created.

The update contains multiple parts:

Exporters

The first part is that we have added two new services, that are used to export the metrics from the lancache-dns and monolithic services.
The two exporters used for this, are the Bind prometheuscommunity/bind-exporter, which converts the bind statistics to a format that can be used by Prometheus, and nginx/nginx-prometheus-exporter, which is used to export the NGINX statistics.

These two exporters are, respectively, community build and official NGINX software. Therefore, we expect them to be maintained and updated in the future, and it is, therefore, adequate to use them here for this use case, instead of building custom exporters and maintaining them.

Network segregation

To build an adequate docker stack for this purpose, and ensure security in the network, we have segregated the network into three parts.

The first part is the main default network. It binds the main services together (lancache-dns and monolithic).

The second network is the dns-metrics network. This handle network connection between the lancache-dns (more specifically bind, and the exposed service on port 8053) and the prometheuscommunity/bind-exporter service.

The third network is the nginx-metrics network. This handles network connection between the monolithic service, and its exposed status service on port 8080, and the nginx/nginx-prometheus-exporter.

By doing it with this segregated network, exporters only have the access that they absolutely need, and no more. Therefore following the principle of least privilege.

This may be simplified, by just using one network, and not following the principle of least privilege.

Healthcheck

To ensure the exporters start correctly, we have implemented health checks on 3 out of 4 of the services in the stack.
The health checks are implemented as a simple curl (for the two Lancache services) and wget (for the prometheuscommunity/bind-exporter) command, that checks that the service is available and running correctly.

The nginx/nginx-prometheus-exporter does not include a health check, due to the container used for this, does not support it.

Healthcecks in general allows for better knowledge of the system status, and in this case, allows us to configure the exporters to only start when the services they are exporting from, are running correctly. This limits the need for restarts.

METRIC_BIND_IP

To help segregate the metrics, and in some form limit the availability of the metrics, we have added a new environment variable to the stack. METRIC_BIND_IP can be set to a specific IP address, that the exporters will bind to. Therefore segregating the metrics to a specific IP address, and not the DNS IP, which is the default IP of the metrics endpoints.

This is documented in both the README.md and the .env file.
In the example file, it is left empty, such that it falls back to DNS_BIND_IP.

Prometheus and grafana

To then use the metrics, Prometheus and Grafana are recommended. This is not included in any of the updates, but is a recommendation for the use of the metrics.

This has shortly been documented in the README.md of the docker-compose repository.

Through the exportes, two new endpoints are available, that can be scraped by Prometheus. One for each Lancache service.

The endpoints are:

As an example, of how this data can be used, we have created a simple Grafana dashboard, that shows the data from the two endpoints.

We are still working on a more complete dashboard, that shows more data, and is more complete. If it is wanted, we can include it in a later update.

Note: The dashboard shown as an example, also uses Cadvisor to show the resource usage of the containers. This is not included in the update and is only shown as an example of how the data can be used.

Pull requests

We have created the following pull requests, to the repositories, that we have mentioned above, from our fork at HTX-LAN

Pull requests:

• lancachenet/lancache-dns#140
• lancachenet/monolithic#181
• #39

Further improvement

The system may not be perfect, and there may be some improvements that can be made. We have already thought of a few elements, and would bring them up, as a part of this issue, as they may depend on the requests of the maintainers.

List of further improvements:

• Patch Docker compose version to support docker compose profiles.
  This would allow for profile launching of the stack, and therefore allow for a more simple setup, and a more complex setup, depending on the needs of the user, through a simple command.
• Update exporters to a newer version, but the current versions are tested to work.
• Documentation on lancache.net website.
  This is not a part of the update, but would be a good addition to the website, to show how the metrics can be used, and document this new feature of the stack.

We are open to any changes that may be needed, in order to conform with the standards of the project and the needs of the maintainers. But we do note, that the current setup, is going to be used in some form, at the next HTX-LAN, and therefore we would like to at least keep the core functionality this adds.

Special thanks go to William Børresen, for being one of the main contributors to this update.

Hi,
I have been doing some test of lancache with the suggested default configuration with docker-compose.yml file. I of course modify the .env conf with my settings and I launch the stack with docker compose.

It is exactly the configuration files from github with the .env modified.

I tested with Steam, Epic launcher, and League of Legends (riot). The steam games are cached by my lancache server, but Epic games or Riot games does not work at all. There is nothing working at all, it is impossible to download anything (the launchers are totaly locked).

On the .env file, I just modified the IP with my server IP, and the DNS by 1.1.1.1. Steam works, the other don't.

Can I do anything ? Is it an issue with lancache ?
Thanks for helping me :)

Used the monolithic version for a while without to many issues.
Recently I moved to the docker-compose version for simplicity.
After a while I came across a problem that my total cache size on disk reduced itself to around 4,5 - 4,6 TB.
While it goes further than that (seen it go to 5,1TB), if the service is restarted, after a while the disk size is reduced again.
Because this does not seem to be intended in the configuration and I am not very good with Linux, I wanted to inform if there is a way to fix this?
First I used the default cache_slice_size of 1m and am using the 8m slice at the moment.
I tried changing the Cache_disk_size from 6000000m to 6000g with no improvement.
Except for the size shrinkage everything seems to be working fine and installing games at 300MB/s is really fun.

My .env config.
USE_GENERIC_CACHE=true
LANCACHE_IP=192.168.2.90 192.168.2.91 192.168.2.92 1692.168.2.93
DNS_BIND_IP=192.168.2.90
UPSTREAM_DNS=192.168.2.1
CACHE_ROOT=./lancache
CACHE_MEM_SIZE=1000m
CACHE_DISK_SIZE=6000g
CACHE_MAX_AGE=3650d
CACHE_SLICE_SIZE=8m

If any other info is needed, please let me know.

Thanks in advance for looking into it.

I've been running lancache for a fair amount of time, working perfectly with Steam. I've just now run across trying to download some games through Epic and receive error code MD-DL-508. Disabling my PiHole's redirection to lancache solves the issue for the time being. I'm not sure how best to parse the logs, but grep'ing access.log shows a few of the following:

[05/Feb/2024:13:39:48 -0600] "GET /Builds/Org/o-4m3t3rbr8yw4rpfdlb6yjppdf6ztbf/d42d7101bb7a41c09a810ee418b7d3d0/default/wk6ucq3Tpr3m_j-rCUCuvRRuzT6znQ.manifest?Policy=eyJTdGF0ZW1lbnQiOiBbeyJSZXNvdXJjZSI6IiovQnVpbGRzL09yZy9vLTRtM3QzcmJyOHl3NHJwZmRsYjZ5anBwZGY2enRiZi9kNDJkNzEwMWJiN2E0MWMwOWE4MTBlZTQxOGI3ZDNkMC9kZWZhdWx0L3drNnVjcTNUcHIzbV9qLXJDVUN1dlJSdXpUNnpuUS5tYW5pZmVzdCIsIkNvbmRpdGlvbiI6eyJEYXRlTGVzc1RoYW4iOnsiQVdTOkVwb2NoVGltZSI6MTcwNzE2MjI4OH0sIklwQWRkcmVzcyI6eyJBV1M6U291cmNlSXAiOiIwLjAuMC4wLzAifX19XX0_&Signature=tgQ6UmeVkflouSShwOrgyeY9zRoqVdxLz6GT3KhCEYb5Mg1uX4K68xSgjuVCXzL7OwzHuFx3lBWOAGT-7O7uzs8mNxX7D5Rkmij~CU2KxKSVJNJ3XMPmwY8e-wsMdZq6nuEIcYKco7UmVPDNi7dgUajjJKqG-rKeB-Fj1i69QLp1pzuT6GyPjqYMY-HW4G1Fnc5CoIdirLG0-ngSt6l-tVWQcLM5dMR8Y6y2cD5IuO5kFAoCaaGbq~fPHS7Y9W8GOAvg0sR8H5ewAXSy4WOWwPS~Z0-JmKZjRuANSkzElxKtNzvWzBGftS--5Csr5JRZKQiCMu44z7zlFKorpSdhyA__&Key-Pair-Id=APKAI5CNFPJPTPYZISXQ HTTP/1.1" 508 0 "-" "EpicGamesLauncher/15.21.1-31156288+++Portal+Release-Live Windows/10.0.22621.1.256.64bit" "MISS" "download.epicgames.com" "-"

Running via docker-compose, just did a fresh install today as I started to dig into this.

Pardon if this has already been solved (didn't see a similar recent issue), but let me know if I can provide further info to help. I know certain clients use https for transfer, but I'm not seeing that in a pcap through Wireshark. Somewhere deep in a thread someone mentioned that Epic may download its initial manifest for a game over https - pure shot in the dark there though.

Thanks!

adding more then one ipstream dns in the .env file breaks the stack.

192.168.1.3 192.168.1.1
192.168.1.3; 192.168.1.1
192.168.1.3:192.168.1.1

These all broke.

I ended up fixing it by edditing the envioment vaiable in portainer for the dns

Hello everybody,

So i installed only the monolithic container because i have 2 DNS server alredy in my network.

So i pointed "lancache.steamcontent.com" to my monolithic host. The DNS resolve is correct. I cleared my Steam Download Cache. But the download is 0kb ore fails with the comment "No Internet Connection". The Steamprefill Downlods with my actual internet speed. But fails in the end. (I have a post in the issues from the prefill client)

So what is wrong?
Pls. Help
Greeting John

Hello, i set up Steamcache on my Synology NAS and everything works fine, although the Download-speed is fairly low. Normally, when i download stuff from Steam, i download with about 10,3-5MB/s and now, i only download with about 5,5MB/s.

I mean, thats not slow, but its still half of my usual download speed. I thought, maybe tweaking nginx would help, but it didnt and now i have no idea. Ressourcemonitor doesnt show anything concerning, everything is ok while downloading and i have enough headroom of cpu, ram and io.

No body is wanting to help me with this... But I really want to get it running on my network. Is there a setting to set this up I have a self signed cert that is on every device that I can use I just need some direction. I have tried alternatives like squid but I edited the config for hours to no avail. Please give me a solution other than go use x software.

TrueNAS does not provide support for Lancache out of the box. In the context of several private events I wanted to use this combination more often and would like to publish my solution here for others with the same problem.
Unfortunately, the pre-built Lancache implementation of Truecharts does not work for me.

1. Adding catalog for docker-compose

Adding the Truecharts catalog to your TrueNAS as described in this manual
https://truecharts.org/docs/manual/guides/Adding-TrueCharts
This takes a few minutes. The progress can be monitored in the task manager.

2. Install an instance of the docker-compose app

Apps -> Available Applications -> docker-compose -> Install
Give it a name like lancache and keep clicking next until you get to the tab Storage and Persistence, click add and select type of storage PVC and mount path to /cache and select the desired storage size for the cache.
Now continue clicking next until you reach the save button and click it.

3. Change WebUi Ports

System Settings -> General -> GUI -> Settings
Change Web Interface HTTP Port and Web Interface HTTPS Port. In my case i use port 8080 and 9443.
From now on you have to use the server address with the new ports for example 192.168.100.100:8080.

4. Setup lancache

Apps -> Installed Applications -> [your new docker-compose instanz] -> three points -> Shell -> Choose
Now you are on the container on which we want to run lancache.
Use the command ls and make sure that the directory cache is present.
Enter the directory with cd cache, create a new directory with mkdir lancache and enter it cd lancache.
Unfortunately this container does not support git but we can download the important files manually.
wget https://raw.githubusercontent.com/lancachenet/docker-compose/master/.env
wget https://raw.githubusercontent.com/lancachenet/docker-compose/master/docker-compose.yml
Open the .env file with nano .env and adjust the configuration. It's important to change your cache path to /cache, your size lower then the seleced size in step 2 and your ip to your truenas ip.
Start the lancache with docker-compose -f docker-compose.yml up -d

5. Check if the cache is running correctly

Write docker ps and check that there are two containers named lancache and lancache-dns.
Go to System Settings -> Shell and type sudo lsof -i -P -n | grep docker and check that there is port 80 (TCP), 443 (TCP) an 53 (TCP+UDP).
Change the DNS server to your truenas ip and disable IPv6 on the device you want to test.
Close steam or whatever applications you want to use to test the cache and open a terminal on the device where you type ipconfig /flushdns.
Now open steam or other game provider and download a game.
While doing this, open the dashboard in the truenas webui and look at the network load. When downloading the game for the first time, the downlink (in) and uplink (out) should match your internet performance and be the same size. The second time you download the game, only the uplink (out) should be used, and at a much higher speed.

I hope I could help someone who had the same problems as me.

Tested under TrueNAS-SCALE-22.02.4

when using localhost ip the cache system doesn't work. the issue seems to resolve itself when using actual ip of box.

With the new Raspberry PI 4 released it would be really nice to have a docker compose file able to run on it. For small LAN parties this would make it really easy to deploy.

Hi

Lancache downloads just stop downloading

So I have installed using socket compose and changed my dns on my pc to the ip I set in setup, when I start a steam download it starts of fine, I can see activity in the access log but after a few minutes it just drops off..

I have experienced this with steam and uplay, I did see to add more ip’s I have gone ahead and done that it has a total of 10 ip’s now but no change.

When I change my dns back to my dns server which in turn is forwarded to 8.8.8.8 & 1.1.1.1 the downloads don’t drop off?

I’m at a loss now, any help would be appreciated.

OS: TrueNAS Scale (I think it's debian based)
With Docker and docker-compose installed: yes

when I try to use docker-compose up -d, I get errors on 'lancache-dns' service

screenshot:

Hey, i just tried to figure out, how to edit the compose file, so i can use different ip adresses for the different services but i am not quite sure, how this works.

Is there a way to do that?

I never used Compose before but i work with Docker, so i am no "newb"

In the .env there is a stipulation that if we're using multiple IPs for the services we need to

Note, If you're using seperate IPs for each service, you may need multiple SNI Proxy containers, one on each IP.

How do we do that?

Hi

I'm recieving the following errors when trying to launch the docker-compose.

Checking nginx config


nginx: [emerg] invalid keys zone size "keys_zone=generic:5g" in /etc/nginx/conf.d/20_proxy_cache_path.conf:1


nginx: configuration file /etc/nginx/nginx.conf test failed


ERROR: hook /hooks/supervisord-pre.d/99_config_check.sh} returned a non-zero exit status '0'

Other than below, everythign is default.

Environmnt is set up like this:

## Set this to true if you're using a load balancer, or set it to false if you're using seperate IPs for each service.
USE_GENERIC_CACHE=true

## IP Address that the lancache load balancer will be running on
LANCACHE_IP=10.245.100.176

DNS_IP=10.245.100.175

## DNS Resolution for forwarded DNS lookups
UPSTREAM_DNS=10.245.110.100

## Storage path for the cached data
CACHE_ROOT=/mnt/md0/lancache

## Which type of steam caching to use [generic|steamcache]
STEAMCACHE_CONTAINER=generic

CACHE_MEM_SIZE=5g
CACHE_DISK_SIZE=100g

and the network configuration:

network:
  version: 2
  renderer: networkd
  ethernets:
    enp3s0f0:
      dhcp4: yes
    enp3s0f1:
      optional: true
    enp4s0f0:
      optional: true
    enp4s0f1:
      optional: true
  bonds:
    bond0:
      interfaces: [enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1]
      dhcp4: yes