The pipe access that the error message mentions is a (probably unrelated) issue when docker client is run by non-admin users (see here). I think the most likely explanation is that the docker service has failed to start. When you ran dockerd you were actually starting an instance of the daemon - and the line API listen on //./pipe/docker_engine means that the system service hadn’t started previously - as the instance you started could create the pipe. ...
If you are seeing this post, it means your blog has been successfully installed.
About the Website No grand introductions here, just bits and pieces Article List Click the title to view the list of articles User Registration If any friends wish to register, click the title to sign up. Welcome to share your thoughts and experiences. About Myself Verbally, my logic struggles to keep up with my thoughts. I prefer practical work over idle speculation and value genuine experiences over empty actions. I enjoy tinkering with new computer-related technologies, both hardware and software. Over the past three years, I’ve built an integrated system—from sensors to microcontrollers to servers—as part of my thesis. I dislike competing for superficial recognition but still want to prove myself. I’ve participated in two mathematical modeling competitions, never achieving the top rank, but the results weren’t bad either. ...