I'm new to setting up a NAS and home lab environment, and I've been struggling with a 'Permission Denied' error. Whenever I try to run the command 'docker compose pull' to open the file where my compose.yaml is located, I get the error: 'open : permission denied'. I'm trying to install Immich on an Ubuntu VM by using SSH with Tailscale and VS Code. I've tried the following commands: 'sudo groupadd docker', 'sudo usermod -aG docker $USER', 'newgrp docker', and even 'sudo docker compose pull', but nothing seems to work. I also switched to the root user, but that didn't help either. Any advice would be greatly appreciated! If there's an easier way to set up Immich on a VM or LXC with Tailscale, I'm open to that as well. Thanks!
3 Answers
Try using the 'chmod' command to adjust the permissions. For example, you could use 'sudo chmod a+rwx ' to grant everyone read, write, and execute permissions. But be cautious with this—it's usually better to adjust file access more specifically rather than just opening it up to everyone! Consider checking the ownership first and only modify access where needed.
Totally agree! It's better to ensure proper ownership instead of broadly adjusting permissions—it can create security risks.
Double-check the permissions for the Docker daemon user. This isn't a direct Docker issue, more of a Linux permissions thing. And if you're on Ubuntu, it's recommended *not* to install Docker via snap—go with the native install. Also, I wouldn't advise running Docker inside an LXC if you’re on Proxmox. If you need alternatives for Immich, check out communities like /r/selfhosted for different setups!
I did some quick research on Immich with Docker, and it seems that if you get a permission denied error, it might be a version issue with Docker. Make sure you're using the correct version since some setups can be finicky. Check the official Immich documentation for installation tips—it might have a straightforward solution!
You can't expect people to read the documentation! *cough* Just kidding; thanks for the tip!
Lol, this actually helped me fix my issue! I realized I was using the default Ubuntu install rather than the command from the docs.
Just running commands like that without explanation can be misleading, especially for beginners. It's essential to be careful with permissions!