dumb-init fails on symbolic link (does it support those?)

Question

dumb-init fails on symbolic link (does it support those?)

Twiggeh opened this issue 3 years ago · 3 comments

I was trying to add an entrypoint to my docker image, but the entrypoint is an arg variable, arising in this issue:

SO issue with docker interpolation issues, suggests to use symbolic links

The solution proposes that I would create a symbolic link and then point dumb-init at said symbolic link.

The only problem appears to be that dumb-init doesn't want to use the symbolic link and throws a "No such file or directory" despite it clearly existing:

(inside the built image)

I have tried version 1.2.2 and 1.2.5

Answer 1 · 2021-08-03T13:07:15.000Z

what does ls -al /usr/bin/brig give you?

Answer 2 · 2021-08-03T13:07:31.000Z

also the term is "symbolic link" by the way

Answer 3 · 2021-08-03T14:56:18.000Z

also the term is "symbolic link" by the way

Thanks :D

what does ls -al /usr/bin/brig give you?

ls -l /usr/bin/service shows that the symbolic link exists. Unfortunately I did not include ls -l /usr/bin/service | grep "brig" that would have shown that the file actually exists.

This doesn't appear to be an issue with dumb-init after further investigation though, because I cannot access that file in any way. It appears to be related to Alpine / something else, so I will close this issue :D