-
Notifications
You must be signed in to change notification settings - Fork 101
20-postfix: redirecting to systemctl start postfix.service #11
Comments
Having the same issue, I was wondering how you removed 20-postfix? |
Same issue here, how to fix? |
You'll need to modify the 20-postfix script to launch postfix directly On Tue, Oct 13, 2015, 23:12 Feng Yu notifications@github.com wrote:
|
It looks like opensuse does something to redirect calls to /etc/init.d scripts to systemd. From /etc/rc.status:
the telltale line is I was able to get phabricator started by defining
I can submit a PR if this is an acceptable solution. |
Yes, that's a good solution. On Wed, Oct 14, 2015, 00:27 robwiss notifications@github.com wrote:
|
I started the container by: docker run -p 80:80 -p 443:443 -p 22:22 -p 22280:22280 -v$(pwd)/config:/config -v $ (pwd)/repo:/srv/repo --name=phabricator --link mariadb:linked_mariadb hachque/phabricator
It failed at
[ STARTING ] /etc/init.simple/20-postfix
redirecting to systemctl start postfix.service
Failed to get D-Bus connection: No connection to service manager.
[ FAILED ] /etc/init.simple/20-postfix
However, the command "/etc/init.d/postfix start" works if I run bash in container, and run it directly.
If I run /init in bash it gives the same error.
After removing 20-postfix, the images works fine though.
The text was updated successfully, but these errors were encountered: