s6-svscan: warning: unable to iopause: Operation not permitted #92
Comments
|
Could you get me the full image digest? For example: I tried to reproduce this just now using the multi-arch runtime support on Docker for Mac and I don't get the same error so I wanted to just make sure it wasn't an issue with a specific image. I currently do not have a raspberry pi with the right architecture available for directly test on. Also, any mount arguments being used for your disk? This one might be a bit challenging as I am not seeing any references to |
|
The drive is being mounted via fstab, here's the line: Here's the full image digest: It's probably something I've done wrong with permissions and fstab - permissions are always a challenge for me. |
|
Well, that's looking about as standard as it gets in terms of a fstab entry - no special mount options and we are running the same image digest so it's the same version. Could you try this image: There is nothing different in those two besides the base image being Alpine 3.13 and 3.12 (instead of |
|
With image With revision 3.12 it appears to be working. |
|
Ah shoot, I forgot about the s6 bug in Alpine 3.13. There might be yet another issue with s6 for armv7l in Alpine 3.14 then. I'll have to see if I can get a Raspberry Pi up and running with armv7l. |
|
I'm more than happy to be your test platform. This is actually a secondary backup, so it's not mission critical, it's mostly because I had a pi running an a spare drive kicking around, so thought "why not?" |
|
Well right now, I am not sure what the problem is exactly. I do have a few older raspberry pis sitting around here somewhere and I probably need to keep one around to test anyway. |
|
Well the only good news is that I can reproduce this fairly easily with a basic run command so you're not doing something wrong: I'm probably going to have to file an upstream bug with Alpine I would guess or it is something specific with something in raspbian as I can't reproduce it when running on Docker for Mac using qemu. |
|
OK, so just keeping some running notes here. There appears to be something related to privileges as running with |
|
It's not privileges - it's And if I pull the backported version of I also tried |
|
So I normally would not suggest installing a package from the Debian repos but the backports |
Signed-off-by: Matt Bentley <mbentley@mbentley.net>
Describe the bug
After pulling the latest version of the docker image, I am unable to get the
smb-armv7lcontainer to start on a Raspberry Pi 3 B+ with an external drive attached. When launching the container, logs indicates6-svscan: warning: unable to iopause: Operation not permittedand it begins a loop.To Reproduce
Steps to reproduce the behavior:
df -Th | grep "^/dev"shows/dev/sda1 ext4 293G 126G 153G 46% /home/pi/externaldocker-compose up -dand view logs.Expected behavior
The logs should show that it has launched successfully, but it loops over and over, as shown in the logs.
How you're launching your container
Run the container using
docker-compose up -dContainer Logs
Additional context
The text was updated successfully, but these errors were encountered: