Jacob Blain Christen

@antoniobeyah after re-reading your use-case I don't see that you need make any code changes at all, you just need to specify the user a la `docker.image('rpm-with-systemd-tester').inside('--user root:root')`. The below...

The trick above is that `docker run` seems to be forgiving of multiple `--user` specifications and the last one in wins. I don't run RPM based images/systems and so if...

@antoniobeyah wrote: > @dweomer That sounds like it may fit your use case, but not mine. I want the containers to start up as they were built, not with an...

@jglick wrote: > Interesting, though it would be nicer to have this be an advertised option. I very much agree. > [JENKINS-38438](https://issues.jenkins-ci.org/browse/JENKINS-38438) was recently filed, which sounds like it is...

@antoniobeyah, I wrote: > I appreciate that you do not wish your PR to get bogged down in design discussion **but your changes, without an opt-in (aka moot the arbitrary...

@sanimej, @dave-tucker: any news on this one? We are looking for this so as to support containerization, with minimal refactoring, of a multicast-based service discovery integration in our stack. We...

The minimal permissions that I needed to get this working were: ``` "s3:Get*", "s3:List*", "s3:PutObject", "s3:PutObjectAcl", "s3:DeleteObject" ``` Which is effectively the default S3 read-only policy plus `PutObject`, `PutObjectAcl`, and...

@brandond I think gaps should be fine as far as the vector clock stuff is concerned but I seem to remember we did have a customer exhaust their key-space (due...

Should we consider [kind](https://kind.sigs.k8s.io/)?

@alexellis I get segfaults when I run on armhf (the arm64 builds work for me with the 64 bit kernel however) and so I am not sure if I am...