kernel version 4.4.0-1090-aws docker file system issue

[Orlix]

When using kernel version 4.4.0-1090-aws
if you have running container and you do sed on some files then you cannot access them inside the container any more

we use the nginx image and we can reproduce it everytime

in the container we have chown and then sed commands on some nginx.conf files
after the sed we are getting persmission denied inside the container even that we use root.

[stentor (stentor-bgyk)]

FYI:
https://lists.gnu.org/r/sed-devel/2019-08/msg00000.html

[Dan Streetman (ddstreet)]

i'm setting this as invalid for linux-aws, as this certainly seems like a sed bug.

[Dan Streetman (ddstreet)]

Unsetting linux-aws back to New, as further investigation seems to indicate there is a kernel bug (as well as sed bug)

[Orlix (orlin-g)]

Update on kernel 1096 and the issue still persist
in our container we run as non-root user
after sed-ing the file persmission are still rw for the user but the nginx cannot read the file
after chmod u+rw file with same user the file is readable again...

E.g.
docker run --rm -ti --entrypoint=bash -u nginx nginx
nginx@5d5453275231:/$ cd /tmp/
nginx@5d5453275231:/tmp$ echo aaa > test
nginx@5d5453275231:/tmp$ cat test
aaa
nginx@5d5453275231:/tmp$ sed -i 's/a/Q/g' test
nginx@5d5453275231:/tmp$ cat test
cat: test: Permission denied
nginx@5d5453275231:/tmp$ chmod u+rw test
nginx@5d5453275231:/tmp$ cat test
QQQ
nginx@5d5453275231:/tmp$