You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apologies if this is not the correct place to raise this issue. Maybe you folks can point me in the right direction. Getting strange behaviour in containers based on debian. This is very beyond my current understanding of linux and docker and all that.
Running on a bare debian image, something is wrong with permissions? ls complains about being able to access anything. Showing below what happens when ls -la is run in / but its consistent everywhere I've tried in the filesystem. Just straight ls works no problem. It works correctly if I go back to buster.
Now while a pain I'd kind of learned to live with it but recently I was working on a dockerfile for something using debian as the base image and I'm also unable to ./execute a script that's built by gnu automake. So I've had to roll the dockerfile back to buster for now. Am I in the right place? or is this perhaps a docker problem?
Thanks!
$ docker pull debian:bullseye-slim
bullseye-slim: Pulling from library/debian
Digest: sha256:b0d53c872fd640c2af2608ba1e693cfc7dedea30abcd8f584b23d583ec6dadc7
Status: Image is up to date for debian:bullseye-slim
$ docker run --rm -it debian:bullseye-slim bash
root@12a49f3bb8b0:/# ls -la
ls: cannot access '.': Operation not permitted
ls: cannot access '..': Operation not permitted
ls: cannot access 'bin': Operation not permitted
ls: cannot access 'boot': Operation not permitted
ls: cannot access 'dev': Operation not permitted
ls: cannot access 'etc': Operation not permitted
ls: cannot access 'home': Operation not permitted
ls: cannot access 'lib': Operation not permitted
ls: cannot access 'lib64': Operation not permitted
ls: cannot access 'media': Operation not permitted
ls: cannot access 'mnt': Operation not permitted
ls: cannot access 'opt': Operation not permitted
ls: cannot access 'proc': Operation not permitted
ls: cannot access 'root': Operation not permitted
ls: cannot access 'run': Operation not permitted
ls: cannot access 'sbin': Operation not permitted
ls: cannot access 'srv': Operation not permitted
ls: cannot access 'sys': Operation not permitted
ls: cannot access 'tmp': Operation not permitted
ls: cannot access 'usr': Operation not permitted
ls: cannot access 'var': Operation not permitted
total 0
d????????? ? ? ? ? ? .
d????????? ? ? ? ? ? ..
d????????? ? ? ? ? ? bin
d????????? ? ? ? ? ? boot
d????????? ? ? ? ? ? dev
d????????? ? ? ? ? ? etc
d????????? ? ? ? ? ? home
d????????? ? ? ? ? ? lib
d????????? ? ? ? ? ? lib64
d????????? ? ? ? ? ? media
d????????? ? ? ? ? ? mnt
d????????? ? ? ? ? ? opt
d????????? ? ? ? ? ? proc
d????????? ? ? ? ? ? root
d????????? ? ? ? ? ? run
d????????? ? ? ? ? ? sbin
d????????? ? ? ? ? ? srv
d????????? ? ? ? ? ? sys
d????????? ? ? ? ? ? tmp
d????????? ? ? ? ? ? usr
d????????? ? ? ? ? ? var
root@12a49f3bb8b0:/#
The text was updated successfully, but these errors were encountered:
There are a few issues here about the problem, but #143 is a pretty recent one - the short answer is that you need to update Docker on your host to 20.10.8+ and libseccomp to 2.4.2+.
Apologies if this is not the correct place to raise this issue. Maybe you folks can point me in the right direction. Getting strange behaviour in containers based on debian. This is very beyond my current understanding of linux and docker and all that.
Running on a bare debian image, something is wrong with permissions?
ls
complains about being able to access anything. Showing below what happens whenls -la
is run in/
but its consistent everywhere I've tried in the filesystem. Just straightls
works no problem. It works correctly if I go back to buster.Now while a pain I'd kind of learned to live with it but recently I was working on a dockerfile for something using debian as the base image and I'm also unable to ./execute a script that's built by gnu automake. So I've had to roll the dockerfile back to buster for now. Am I in the right place? or is this perhaps a docker problem?
Thanks!
The text was updated successfully, but these errors were encountered: