IPv6 not enabled on host breaks the container

Issue #68 wontfix
Michael Shadle created an issue

I don't have ipv6 enabled (internal company LAN) and the container instance services all fail.

I know people want ipv6 support, but it shouldn't break those without ipv6. Still trying to see if I can figure out any way around it.

2016-03-22 16:44:11,354 INFO exited: nginx (exit status 1; not expected)
2016-03-22 16:44:11,418 INFO exited: dovecot (exit status 89; not expected)
2016-03-22 16:44:11,560 INFO exited: qpsmtpd-forkserver (exit status 97; not expected)
2016-03-22 16:44:12,562 INFO success: spamd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-03-22 16:44:12,562 INFO success: php5-fpm-admin entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-03-22 16:44:12,562 INFO success: qmail-send entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-03-22 16:44:12,562 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-03-22 16:44:12,563 INFO spawned: 'nginx' with pid 192
2016-03-22 16:44:12,564 INFO success: clamd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-03-22 16:44:12,564 INFO success: rsyslog entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-03-22 16:44:12,566 INFO spawned: 'qpsmtpd-forkserver' with pid 193
2016-03-22 16:44:12,568 INFO spawned: 'dovecot' with pid 194
2016-03-22 16:44:12,568 INFO success: php5-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-03-22 16:44:12,582 INFO exited: nginx (exit status 1; not expected)
2016-03-22 16:44:12,621 INFO exited: dovecot (exit status 89; not expected)
2016-03-22 16:44:12,748 INFO exited: qpsmtpd-forkserver (exit status 97; not expected)
2016-03-22 16:44:14,752 INFO spawned: 'nginx' with pid 198
2016-03-22 16:44:14,754 INFO spawned: 'qpsmtpd-forkserver' with pid 199
2016-03-22 16:44:14,756 INFO spawned: 'dovecot' with pid 200
2016-03-22 16:44:14,770 INFO exited: nginx (exit status 1; not expected)
2016-03-22 16:44:14,811 INFO exited: dovecot (exit status 89; not expected)
2016-03-22 16:44:14,941 INFO exited: qpsmtpd-forkserver (exit status 97; not expected)
2016-03-22 16:44:17,976 INFO spawned: 'nginx' with pid 203
2016-03-22 16:44:17,983 INFO spawned: 'qpsmtpd-forkserver' with pid 204
2016-03-22 16:44:17,985 INFO spawned: 'dovecot' with pid 205
2016-03-22 16:44:17,995 INFO exited: nginx (exit status 1; not expected)
2016-03-22 16:44:18,024 INFO gave up: nginx entered FATAL state, too many start retries too quickly
2016-03-22 16:44:18,044 INFO exited: dovecot (exit status 89; not expected)
2016-03-22 16:44:18,170 INFO gave up: dovecot entered FATAL state, too many start retries too quickly
2016-03-22 16:44:18,171 INFO exited: qpsmtpd-forkserver (exit status 97; not expected)
2016-03-22 16:44:19,173 INFO gave up: qpsmtpd-forkserver entered FATAL state, too many start retries too quickly

Comments (4)

  1. SH repo owner

    I am not sure i will ever fix this. All docker hosts should be ipv6 capable afaik, so it is much easier to setup at least local ipv6 address than adding unnecessary amount of code which will be handling all daemons configs.

    There is one solution though, you can change every failing daemon config by adding customized config to /data/_override/(...absolute path in container). BUT it might break with new versions.

  2. Michael Shadle reporter

    if the host doesn't have it, I don't think the containers do. if it's not easy to do, I guess I will have to look at trying to get the host to have ipv6 and not break something internally.

  3. Log in to comment