consider ignoring non-regular,non-symlink files in /etc
#2446
Comments
cgwalters
added a commit
to cgwalters/ostree
that referenced
this issue
Oct 1, 2021
https://bugzilla.redhat.com/show_bug.cgi?id=1945274 is an issue where a privileged kubernetes daemonset is writing a socket into `/etc`. This makes ostree upgrades barf. Now, they should clearly move it to `/run`. However, one option is for us to just ignore it instead of erroring out. Some brief investigation shows that e.g. `git add somesocket` is a silent no-op, which is an argument in favor of ignoring it. Closes: ostreedev#2446
cgwalters
added a commit
to cgwalters/ostree
that referenced
this issue
Oct 1, 2021
https://bugzilla.redhat.com/show_bug.cgi?id=1945274 is an issue where a privileged kubernetes daemonset is writing a socket into `/etc`. This makes ostree upgrades barf. Now, they should clearly move it to `/run`. However, one option is for us to just ignore it instead of erroring out. Some brief investigation shows that e.g. `git add somesocket` is a silent no-op, which is an argument in favor of ignoring it. Closes: ostreedev#2446
cgwalters
added a commit
to cgwalters/ostree
that referenced
this issue
Oct 1, 2021
https://bugzilla.redhat.com/show_bug.cgi?id=1945274 is an issue where a privileged kubernetes daemonset is writing a socket into `/etc`. This makes ostree upgrades barf. Now, they should clearly move it to `/run`. However, one option is for us to just ignore it instead of erroring out. Some brief investigation shows that e.g. `git add somesocket` is a silent no-op, which is an argument in favor of ignoring it. Closes: ostreedev#2446
cgwalters
added a commit
to cgwalters/ostree
that referenced
this issue
Oct 1, 2021
https://bugzilla.redhat.com/show_bug.cgi?id=1945274 is an issue where a privileged kubernetes daemonset is writing a socket into `/etc`. This makes ostree upgrades barf. Now, they should clearly move it to `/run`. However, one option is for us to just ignore it instead of erroring out. Some brief investigation shows that e.g. `git add somesocket` is a silent no-op, which is an argument in favor of ignoring it. Closes: ostreedev#2446
cgwalters
added a commit
to cgwalters/ostree
that referenced
this issue
Oct 1, 2021
https://bugzilla.redhat.com/show_bug.cgi?id=1945274 is an issue where a privileged kubernetes daemonset is writing a socket into `/etc`. This makes ostree upgrades barf. Now, they should clearly move it to `/run`. However, one option is for us to just ignore it instead of erroring out. Some brief investigation shows that e.g. `git add somesocket` is a silent no-op, which is an argument in favor of ignoring it. Closes: ostreedev#2446
cgwalters
added a commit
to cgwalters/ostree
that referenced
this issue
Oct 1, 2021
https://bugzilla.redhat.com/show_bug.cgi?id=1945274 is an issue where a privileged kubernetes daemonset is writing a socket into `/etc`. This makes ostree upgrades barf. Now, they should clearly move it to `/run`. However, one option is for us to just ignore it instead of erroring out. Some brief investigation shows that e.g. `git add somesocket` is a silent no-op, which is an argument in favor of ignoring it. Closes: ostreedev#2446
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://bugzilla.redhat.com/show_bug.cgi?id=1945274 is an issue where a privileged kubernetes daemonset is writing a socket into
/etc. This makes ostree upgrades barf.Now, they should clearly move it to
/run.However, one option is for us to just ignore it instead of erroring out. Some brief investigation shows that e.g.
git add somesocketis a silent no-op, which is an argument in favor of ignoring it.The text was updated successfully, but these errors were encountered: