Sorry, had just gone into an interview. ping was j...
# choria
b
Sorry, had just gone into an interview. ping was just the example, ultimately this would be to call mco agent functions from within the rootless container. Had already been doing this long term in a rootful container using user-squashing to run the container processes as non-root uid which mco was fine with. But am now moving to a rootless container platform, so the container processes will now run as namespaced uid 0. This is not really root, and has permissions ~equivalent to the permissions the user launching the container holds, and ~equivalent permissions to the non-root uid in the old rootful. So it's a somewhat arbitrary restriction in mcollective-choria in that I'm not significantly changing my security domain but can't now do the thing I was before. I totally get the decision not to allow mco to run as host uid 0. For the moment I've hacked out the line from the ruby code with sed at container build time, which is probably fine long term. Running choria/puppet inside the container was a bit of a bodge anyway 😄