-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Errno 13] Permission denied: '/dev/stdout' #88
Comments
Same here |
what os are you trying this on? |
Running it as a container on a Synology NAS, 1821+ in my case. |
Docker 26.0.1 @ Debian 12.5 |
Same here using docker 26.1.0 under Ubuntu Server 22.04 |
Is the latest update from f299da8 fixing this? I can't recreate the issue on Ubuntu 24.04 with Docker 26.1.0. |
Doesn't seem to for me - I pulled
|
@c-hri-s, are you sure this is latest? It should be writing to |
Still can't start the container. The error is different, though Apparently the supervisor is running under an unprivileged user while trying to access root-restricted areas inside the container (or using unchanged UID / GID because it doesn't have the rights to do so). I run docker service as root and synology DSM does the same, as far as I remember.
|
Does it fail the same way if you run the container with PUID=0 and PGID=0, @dr3nch? |
Hello! With PUID=0 and PGID=0 works without problem. With PUID=1000 and PGID=1000, now, the error its: PermissionError: [Errno 13] Permission denied: '/proc/self/fd/1' Thanks! Edit1: I said this in Ubuntu 24.04 |
Works for me on Synology with |
Running everything inside the container as root (PUID/PGID 0) is suboptimal for security. It would also change the ownership of all files mounted to root. I don't have access to a Synology setup to test what works best there but I wonder if it now works on Debian without elevating to root, @dr3nch? |
@R4di04kt1v3, works fine on 24.04 over here. Just tested on a different VPS:
|
With PUID-PGID 0 works without problem. With PUID-PGID 1000 not, at least for now... since the last update... You are with PUID-PGID 1000 ? |
OK, not sure why I assumed the default PUID/PGID are 1000, this is how it fails:
|
Yeah, same error here... The problem its PUID/PGID 1000 in the last update... |
Also seeing this issue in the latest tag.
A bit annoying, the docker hub does not seem to use different tags, so once we update to :latest, we're stuck :( |
Debian 11 user (latest packages + Docker version 20.10.5+dfsg1, build 55c4c88) here, it does not in fact work with PGID/PUID 1000
|
Thanks for the feedback. An update is in the works, in the meantime running as PUID=0 and PGID=0 should get it going. |
@realies cheers / thank you |
Also experiencing this on manjaro (arch-based). Sidenote: please add a donation link/button to your profile @realies I use your containers pretty much every day and would like to make a small donation :) |
Can you check if the latest build runs fine without PUID=0 and PGID=0? There's also a support me button on my profile page now :) |
Yep, it works 🎉 |
Now works like a charm! Thanks a lot @realies !! |
It works! |
Hello! In my case, shared folder it's working with last update and 1000:1000 permission |
Did some more testing and downloading is also not working for me. My docker compose file (didn't include gluetun config because it's not relevant):
Error log (transfer queue) from soulseek:
File permissions of host folder
Same permissions for all child folders. Am I missing something here? |
ditto, works here too. edit: @TristanK27 not having that issue here, must be isolated to your setup/config. |
@TristanK27, I wonder if it's somehow related to the way the external disk is mounted. Can you double check you can't create files here I think you can try changing the permissions of your folders from
Edit: another possibility is a strange behaviour with the default umask value. |
I've just pushed an update which:
The default umask of 022 should give all |
I can touch files just fine, as wel as read them within the container. Edit: I didn't refresh the page before writing this comment, please ignore. |
Last update fixes it! |
Bit late to the party but it's all fixed for me too! Thanks for the quick fix! |
After pulling the last image I can't start my soulseek container. It always exits with
[Errno 13] Permission denied: '/dev/stdout'
. A container deployed 4 days ago on another host works just fine. Presumably it's related to 90871edI'd pull a previous version, but there is only
latest
image on Docker Hubdocker-compose.yml
docker compose up
The text was updated successfully, but these errors were encountered: