Why am I always stuck here?

[imowen]

[melalj]

Same here

2020-10-09T14:35:20.797541975Z [services.d] starting services
2020-10-09T14:35:20.802049332Z [2020-10-09T14:35:20.801942] WARNING: Configuration file format is too old, syslog-ng is running in compatibility mode. Please update it to use the syslog-ng 3.27 format at your time of convenience. To upgrade the configuration, please review the warnings about incompatible changes printed by syslog-ng, and once completed change the @version header at the top of the configuration file; config-version='3.9'
2020-10-09T14:35:20.804350977Z Oct 9 14:35:20 05a8de51e653 syslog-ng[622]: syslog-ng starting up; version='3.27.1'
2020-10-09T14:35:20.804361516Z Oct 9 14:35:20 05a8de51e653 syslog-ng[622]: WARNING: log-fifo-size() works differently starting with syslog-ng 3.22 to avoid dropping flow-controlled messages when log-fifo-size() is misconfigured. From now on, log-fifo-size() only affects messages that are not flow-controlled. (Flow-controlled log paths have the flags(flow-control) option set.) To enable the new behaviour, update the @version string in your configuration and consider lowering the value of log-fifo-size().;
2020-10-09T14:35:20.807627282Z [services.d] done.
2020-10-09T14:35:20.836509088Z Oct 9 14:35:20 05a8de51e653 postfix/postfix-script[646]: stopping the Postfix mail system
2020-10-09T14:35:20.837357541Z Oct 9 14:35:20 05a8de51e653 postfix/master[97]: terminating on signal 15
2020-10-09T14:35:21.048454491Z Oct 9 14:35:21 05a8de51e653 postfix/master[712]: daemon started -- version 3.5.7, configuration /etc/postfix
2020-10-09T14:35:22.451938354Z [s6-finish] sending all processes the KILL signal and exiting.

[CarterStClair]

I'm seeing the same issue running it in AWS. Works fine on my local Windows Docker instance.

[drpreag]

Similar here.

[services.d] starting services
[2022-01-05T15:27:52.015045] WARNING: Configuration file format is too old, syslog-ng is running in compatibility mode. Please update it to use the syslog-ng 3.27 format at your time of convenience. To upgrade the configuration, please review the warnings about incompatible changes printed by syslog-ng, and once completed change the @Version header at the top of the configuration file; config-version='3.9'
Jan 5 15:27:52 d5a673c4b89d syslog-ng[903]: syslog-ng starting up; version='3.27.1'
Jan 5 15:27:52 d5a673c4b89d syslog-ng[903]: WARNING: log-fifo-size() works differently starting with syslog-ng 3.22 to avoid dropping flow-controlled messages when log-fifo-size() is misconfigured. From now on, log-fifo-size() only affects messages that are not flow-controlled. (Flow-controlled log paths have the flags(flow-control) option set.) To enable the new behaviour, update the @Version string in your configuration and consider lowering the value of log-fifo-size().;
[services.d] done.