Press question mark to learn the rest of the keyboard shortcuts Log in sign up User account menu 3 Docker Desktop macOS starting at boot.My use case here is having a remote desktop mac to use with my iPad Pro, and to save money, to see if it could replace my Linode VPS, which runs everything inside Docker.
Docker Desktop can be set to run as an app at login, and when its running I get docker, docker-compose, etc all on the command line over SSH just like my linode. But my google skills must be weak because I see a lot of people asking about running it at boot, and not login, and bunch of launchctl gets mentioned with limitations. Most threads are so old it refers to VirtualBox which I believe isnt used anymore. Maybe Im missing something here, but how do I run Docker on Catalina in a way I can just use command line tools similar to Linux, but which doesnt require a user logged in on the desktop I can set a user to autologin at boot, but Id rather not have VNC being the only security between the internet and a fully logged in desktop. Upvoted Log in or sign up to leave a comment log in sign up Sort by best no comments yet Be the first to share what you think View entire discussion ( 0 comments) More posts from the docker community Continue browsing in rdocker rdocker Docker( ) is an open-source project to easily create lightweight, portable, self-sufficient containers from any application. The same container that a developer builds and tests on a laptop can run at scale, in production, on VMs, bare metal, OpenStack clusters, public clouds and more. Members 171 Online Created Jul 26, 2013 Join help Reddit App Reddit coins Reddit premium Reddit gifts about careers press advertise blog Terms Content policy Privacy policy Mod policy Reddit Inc 2020. All rights reserved Back to top. Having to scan the file system for different ACL entries in a burden for those doing a security audit, but it prevents you from having to use the docker group entirely. While youll want to ensure that it is, youll probably be puzzled when you find out that this error doesnt even have to do with the service not being started. It mostly gets thrown at users who havent added themselves to the Docker group. Docker issues a separate user group on Linux systems, and those who have user accounts that arent added to it wont be able to connect to it. Keep in mind that adding a user account to the Docker group is functionally root equivalent since the daemon is always running as the root user. This might be expected on a single-user Ubuntu Server system, but it will certainly be something to keep in mind for those running Docker on Arch, Fedora or Debian. Method 1: Checking Docker Service Status While it almost certainly is, youll need to check if the Docker service is currently running. At a terminal window, run systemctl status docker.service as a normal user. You should get some information about which PID number Dockers daemon got assigned. Should you have restarted it, try doing whatever it was that threw you the cannot connect to the Docker daemon error. If it now works, then you just didnt have the service running and dont really need to worry about anything else besides the reason it wasnt running. Unfortunately, this doesnt work in a majority of cases so youll need to move on in those situations. Method 2: Adding Users to the Docker Group Run docker info from the command line, which will normally give you the cannot connect to the Docker daemon error once again. If this is the case, then youll need to run sudo groupadd docker; sudo usermod -aG docker USER to add yourself to the proper group. Should this give an error because you dont have usermod, then you can modify the command to run as sudo groupadd docker; sudo gpasswd -a USER docker, but this generally shouldnt be an issue because most commercial-grade Linux distributions are working with the same set of tools. In any case, run newgrp docker so you can get logged into the new docker group if youre not already. ![]() Since you have administrative access keyed in for the time being, run sudo chgrp docker usrbin docker; sudo chgrp docker varrundocker.sock to fix the permissions on the docker socket and command. Usually, the socket file belongs only to the root user so this will correct that. After having run it, you shouldnt have any trouble because it now belongs to the same group that you had created in the previous command. Youll want to test to ensure that docker runs without sudo, though, so type docker run hello-world as a regular user to make sure youre not getting any other errors. At this point, very few users will still be receiving any sort of error message. Most things should be corrected at this point, but if youre still having problems you might want to completely log out. Try opening another terminal emulator window, but if this doesnt work it sometimes help to bring the system down for a complete restart if thats at all feasible Method 3: Using ACLs to Modify Docker Metadata If you dont want to belong to a group that makes you like a root user, then you can set the socket file to work with only certain permissions. You can ignore the gpasswd process if youd prefer to do it this way.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2020
Categories |