Support podman in tasks/build.rake#227
Conversation
|
I opened #228 before I noticed this PR. The approach there is even simpler, but requires the use of the Building other OpenVox components, such as |
|
No worries. Any interest in me reworking this to remove the dependency on the shim? |
|
Using environment variables to pick a CLI implementation seems reasonable to me. Perhaps |
6a79a0b to
cba84c5
Compare
cba84c5 to
5bcc181
Compare
Sharpie
left a comment
There was a problem hiding this comment.
Looks good to me 👍
Thanks for the contribution!
Head branch was pushed to by a user without write access
b7e5863 to
03e9260
Compare
|
Hi, so I can keep the PR up to date with respect to main (which I did just now with a force push), but I don't know the procedure for actually merging the PR. Auto-merge was enabled prior to my last push, but I wasn't able to merge it at that time. Is two committers' approval needed for a PR to be merged? |
|
@gregorynisbet-google sorry for the delay here! I would like to get this merged, but run into some issues. The rake task fails with: Did you run the podman service as user service or as root? |
|
I'm running it rootless, which is the default out of the box on my platform. For me, at least, running I'm not sure what could cause this PR to fail with some kind of permission issue when run in CI (or locally) in an environment where The only thing I can think of is some change to the behavior of the build system when passing the format argument to |
Split OpenVoxProject#227. Signed-off-by: Greg NISBET <gregorynisbet@google.com>
Support podman in addition to docker in tasks/build.rake via the DOCKER environment variable. Signed-off-by: Greg NISBET <gregorynisbet@google.com>
03e9260 to
a63b99c
Compare
Support podman in addition to docker in tasks/build.rake via the DOCKER environment variable.
Pull Request (PR) description
I did the simplest thing I could think of to make
DOCKER=podman rake vox:buildsucceed.There are a few differences between
--format jsonfor Docker and podman, but I still thinkthat that's the most robust way to get the commands to emit structured output.
I'm curious whether folks think this is worth doing at all, and whether an environment variable
is the best way of achieving this (and also whether shell substitution is better than doing the
conditional at the ruby level)
This Pull Request (PR) fixes the following issues
n/a