Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Is there a way to start runit
See original GitHub issueHi,
I was wondering if it was possible to combine this with runit, explicitly making this container work: https://github.com/dockage/alpine-runit/blob/master/Dockerfile#L29 I have tried all kind of things like replacing the CMD with:
ENTRYPOINT ["/usr/bin/dumb-init", "--"]
CMD ["/sbin/runit-init"]
But when I use the above and I start the container I get usage: /sbin/runit-init 0|6.
I could get it to work with CMD ["runsvdir", "-P", "/service"], but I would like to use the files that are being used by the image in /etc/runit (see https://github.com/dockage/runit-scripts/tree/master/alpine/etc/runit).
So is there a way to get this to work?
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@Ilyes512 I have explained how to start runit in another issue. https://github.com/Yelp/dumb-init/issues/158#issuecomment-369358986
I realize you’re trying to use runit differently but just adding another concrete example of runsvdir.
@samrocketman I already solved this and I probably came across your answer back then 😃.
Thanks! I am closing this.