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$

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sed in Ubuntu.
https://bugs.launchpad.net/bugs/1841058

Title:
  kernel version 4.4.0-1090-aws docker file system issue

Status in linux-aws package in Ubuntu:
  New
Status in sed package in Ubuntu:
  New

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1841058/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to