We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
foobar
Dockerfile
foobar:foobar
$ docker run -v "${PWD}":/run safewaters/docker-lock lock generate
Actual: generate docker-lock.json with owner group root:root, if there is an empty docker-lock.json, permission is OK.
docker-lock.json
root:root
Expected: generate owner group as first matched files owner group
$ docker run -v "${PWD}":/run safewaters/docker-lock lock rewrite
Actual: changed Dockerfile from foobar:foobar to root:root
Expected: owner group unchanged
The text was updated successfully, but these errors were encountered:
Workaround, non-root
$ podman run -v "${PWD}":/run docker.io/safewaters/docker-lock lock generate $ podman run -v "${PWD}":/run docker.io/safewaters/docker-lock lock rewrite
Sorry, something went wrong.
No branches or pull requests
Given
foobar
haveDockerfile
with owner groupfoobar:foobar
Problems
$ docker run -v "${PWD}":/run safewaters/docker-lock lock generate
Actual: generate
docker-lock.json
with owner grouproot:root
, if there is an emptydocker-lock.json
, permission is OK.Expected: generate owner group as first matched files owner group
$ docker run -v "${PWD}":/run safewaters/docker-lock lock rewrite
Actual: changed
Dockerfile
fromfoobar:foobar
toroot:root
Expected: owner group unchanged
The text was updated successfully, but these errors were encountered: