Problem with tty when using su-exec inside a docker

[atanmarko]

I have an use-case where I execute su-exec command from the entrypoint.sh script inside docker. Problem is that executed program can not open default tty device (in my case '/dev/pts/0') because it is still owned by root while su-exec command is running.

I did a workaround by manually changing ownership of tty device before running command, but maybe this could be resolved in su-exec?

[tianon]

I'd add a link to tianon/gosu#8 which has some very relevant discussion around this same idea. 😅

[atanmarko]

Similar thing is happening in login utility, you can check how they chown tty here