Closed dosfx closed 2 years ago
There are a few issues here about the problem, but https://github.com/debuerreotype/docker-debian-artifacts/issues/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+.
@tianon thanks dude too easy. Sorry to bother you!
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!