-
-
Notifications
You must be signed in to change notification settings - Fork 254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Streams broken by stream.conf #440
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Just remove |
Thanks, just saw that. That drops out the log lines in /etc/nginx/conf.d/stream.conf, however. I'm sure that's not a big deal, however it would be cleaner in whatever the next release is to fix that, and I didn't see it documented anywhere. Thank you for the lightning fast response! |
It's part of the upstream Alpine nginx package and not a change we've made intentionally. |
Gotcha. Could it be handled the same way nginx.conf is handled? In /etc/nginx/nginx.conf, everything is deleted and only "include /config/nginx/nginx.conf;" is in the file. Could /etc/nginx/conf.d/stream.conf be changed the same way to only have "include /config/nginx/stream.conf;" in it, then the current contents of /etc/nginx/conf.d/stream.conf can be moved to /config/nginx/stream.conf, and the user can add whatever they need? Just a thought. I'm honestly still not sure how I figured out the problem at all, as I'm not usually one to poke around in the docker filesystem. Thanks again. |
We don't want anything to do with stream. We delete the stream.conf in the baseimage so the user can add theirs if they like. Sounds like upstream changed the location of it (on mobile, didn't look, only guessing) so we'll have to update it to delete again. |
That would solve the problem. Thanks! |
We're deleting it on the base but it's being added back by installing https://github.com/linuxserver/docker-swag/blob/master/Dockerfile#L45 in the downstream image. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
Is there an existing issue for this?
Current Behavior
I upgraded to a more recent SWAG and my stream directive (added after the http directive in nginx.conf) was broken because it was suddenly a duplicate. Digging into the docker volume, there is now a stream directive in /etc/nginx/conf.d.
This directive has an include for anything added to /etc/nginx/stream.d as a .conf file, but I don't see any way to add this in the config folder, making it impossible to use a stream directive outside of tampering with the docker volume filesystem
Expected Behavior
I should be able to add stream directive blocks somewhere in the /config/nginx directory (stream-confs?) that are then added to the stream directive in /etc/nginx/conf.d/stream.conf
There are a number of ways to do this that I'm sure y'all understand. The simplest would be to add streams.conf to the /config/nginx folder, then add
include /config/nginx/streams.conf
to /etc/nginx/conf.d/stream.conf. The stream server blocks could all be added to that single .conf file.Steps To Reproduce
Add a stream directive anywhere in the config folder.
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: