@mafintosh I don't think the shell docker implementation is going to work anytime soon; we've been repriotizated, it's pretty close tho
-
-
Replying to @yoshuawuyts
@mafintosh step that's missing is attaching to a running container after it's been started; need to do direct system calls for that :(2 replies 0 retweets 0 likes -
Replying to @yoshuawuyts
@yoshuawuyts i''m sure i know what you mean by this1 reply 0 retweets 0 likes -
Replying to @mafintosh
@mafintosh are you sure or not sure? Talking about project I showed you a few weeks ago; not sure if still relevant https://github.com/stamf/shocker1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
@yoshuawuyts haha sry i meant not sure :) when do you need to "attach to a running container after it's been started" ?1 reply 0 retweets 0 likes -
Replying to @mafintosh
@mafintosh oh yeah, right. So we can run commands inside the namespace / cgroups, but they're not being owned by pid 1 (e.g. init) :(2 replies 0 retweets 0 likes -
Replying to @yoshuawuyts
@mafintosh it's been a while, but supposedly there was a workaround using system calls to manipulate that; but no known CLI tools expose it1 reply 0 retweets 0 likes
@mafintosh the only way to do things is to start everything on init / provide config files; but that makes it non interactive :(
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.