1/20/2024 0 Comments Sudo not found synology![]() The socket ( docker.sock) in /var/run/ was owned by root as user and root as group. Srw-rw- 1 root root 0 Jun 10 17:40 docker.sock rw-r-r- 1 root root 5 Jun 10 17:40 docker.pid However, there was an extra step needed on DSM, to actually assign to this new docker group access to the Unix socket that Docker uses.īefore I did this, I wanted to see what the standard situation was: ls -l /var/run/ | grep dockerĭrwx- 8 root root 200 Jun 10 17:40 docker ![]() The Manage Docker as a non-root user steps mentioned earlier showed that this is pretty much all one needs to do on a standard Docker-on-Linux install. Change the group owner of the Docker socket ![]() Great, the docker group now exists, with administrator as a member. Time to create the group then, using the DSM specific command I specified the administrator user to be added directly, as I did it: sudo synogroup -add docker administratorĬhecking to see if the group was now listed in /etc/group confirmed that these DSM specific commands weren't doing anything out of the ordinary: grep -i docker /etc/group Add the docker group, with the administrator user as a member Check docker group doesn't already existįirst, I wanted to check that I wasn't about to clobber any existing docker group: grep -i docker no existing docker group, at least in the regular place. I'm a check-before-and-after kind of person, so some of these steps aren't essential, but they helped me to go carefully. They all begin syno and are described in the CLI Administrator Guide for Synology NAS. In fact, there are DSM specific commands for managing local users, groups, network settings and more. However, due to the way that users and groups are managed in DSM, this specific approach didn't work there was no docker group that had been created, to which the administrator user could be added, and manually adding the group wasn't the right approach either, not least because DSM doesn't sport a groupadd command. In the standard Docker Post-installation steps for Linux, there's a specific section for this: Manage Docker as a non-root user. The first thing I wanted to do is to allow myself to run the docker CLI as a non-root user in my case (as in many basic Synology NAS contexts) this is the as the administrator user. Linuxserver/freshrss latest 09ffc08f14fe 4 weeks ago access as non-root user Homeassistant/home-assistant latest 832ca33fe14a 4 weeks ago 1.1GB directly, or via sudo as shown in this example: ssh sudo docker -vĭocker version 20.10.3, build sudo docker image ls Here's what I did, starting from the Docker package already installed and running on the NAS.įrom a command line perspective, this out of the box installation also gave me access to be able to run the docker client CLI while remotely logged into the NAS, but only as root, i.e. Not only for the sheer convenience, but also to be able to spin up CLIs and TUIs, as remote containers, and have seamless access to them from the comfort of my local machine's command line. So I wanted to use my Docker command line interface (CLI) docker to interact with the resources on the Synology NAS's Docker service. I've been very happy with the way it works, especially in the initial discovery phase.īut for this old mainframe and Unix dinosaur, a command line interface with access to a myriad remote servers is a much more appealing prospect, and the separation of client and server executables in Docker plays to the strengths of such a setup. The Docker experience out of the box with the NAS's operating system, DiskStation Manager (DSM), is very pleasant, via a graphical user interface. ![]() This was one of the reasons I opted for a Synology NAS, my first NAS device (see Adding a drive to my Synology NAS), because it is to act not only as a storage device, but as a container server. Having followed the container revolution for a while, I've become more and more enamoured with the idea of disposable workspaces, services and apps that can be instantly reified and leave no trace when they're gone. It was a little less obvious than one might have expected, because of the way the Docker service is hosted on the NAS's operating system, and I ended up having to read around (see the reading list at the end). There are other approaches, but this is what I did. This post describes the steps I took to set up remote access to Docker running on my NAS, in the simplest and "smallest footprint" possible way I could find. Here's what I did to enable remote access to the Docker install on my Synology NAS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |