oh-bee

I think, that this is not only a valid (and unanswered) question but also a valuable "enhancement request". Not only for Graylog use case ... from me: +1 Because rsyslog config via GUI is very rudimentary, an option to use a custom rsyslog.conf could be helpful. Is there a recommendation to tune rsyslog via snippets in /etc/rsyslog.d/*.conf Best regards Oliver

I also want to say thx to @maciekish and I also agree to the opinion of @Indmenity83 : "sticking with this after the responses he got". I read the post from the beginning to the end and every single follow up of all these "I know your requirements better than you"-guys, I thought: wtf ...

Thank you. For me it works, because I always assign manually an IP but ... if @saarg is right, I think the downgrade to "other" isn't correct.

It seems that I had a basic misunderstanding with ports to expose and macvlan. Sorry ... Because it's the first time I created a container on my own without using a template, I did not realize, that I don't have to expose ports, because this configuration was done automatically ... without any needs. Thx a lot for clarification. Than this"bug is only a "gui problem" with a "layer 8 error"

Unraid version: 6.7.2 and 6.8 Browser: same with Firefox and Edge. Did not test more. Steps to reproduce: 1. Docker 2. add container 3. configure custom network (macvlan at me) 4. add another path/port/... 5. see screenshots Occurrance: only with custom network. As I ever use my macvlan network I didn't realize that. Urgent: change it to whatever you mean, because there is a workaround with: 3) "configure bridge network" 4..n) "fulfill exposed ports" n+1) "change network to custom"