I'm having a frustrating issue with Docker on my TrueNAS SCALE server. While I can easily pull the `nginx:latest` image using `sudo docker pull nginx:latest`, I'm hitting a wall when I try to pull other public images like `docker.io/linuxserver/netboot.xyz:latest`. The command fails, giving me a 'pull access denied' error and suggesting that I might need to log in to Docker. I checked my `/etc/docker/daemon.json`, and everything seems normal—no registry mirrors set up. Can anyone shed light on why my Docker daemon is treating certain community images differently and directing those requests to an authenticated registry? Any guidance would be greatly appreciated!
1 Answer
It seems like the error you're encountering may be related more to Docker's ability to communicate through the Docker API rather than just an issue with pulling an image. First, check what `docker ps` outputs—if it shows a similar error, it indicates Docker might not be running properly. Also, make sure your user is part of the Docker group, or else you'll need to run commands with `sudo`. You might want to test pulling a simpler image like `docker pull busybox:latest` to see if that works. Either way, it sounds like there's a communication hiccup rather than a problem with the image pull itself.
Yeah, adding the user to the Docker group sounds like the way to go, but if you're having trouble with that, you could create a new user that has the necessary permissions or find someone who's already in that group. It’s puzzling, especially since you've managed to pull an image before!