Last active
November 25, 2018 14:04
-
-
Save yeungon/740e1b11acb1ac470ddef08af6cedbb0 to your computer and use it in GitHub Desktop.
Ubuntu from the scratch (for Vietnamese)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Một hướng dẫn chi tiết về docker
https://www.codehub.vn/Lam-the-nao-de-cai-dat-va-su-dung-Docker-tren-Ubuntu-18-04
Cách đơn giản để chạy LAMP với docker
Docker tiếp theo: https://viblo.asia/p/docker-for-beginner-part-ii-3P0lPAqv5ox
Delete all docker containers
docker rm $(docker ps -a -q)
Delete all docker images
docker rmi $(docker images -q)
How docker ps helped me: docker rm -f $(docker ps -aq) is a short command which I use to remove all containers.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Chú ý lỗi
Problem:
You are trying to run a docker container or do the docker tutorial, but you only get an error message like this:
docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.26/containers/create: dial unix /var/run/docker.sock: connect: permission denied.
See 'docker run --help'.
Solution:
The error message tells you that your current user can’t access the docker engine, because you’re lacking permissions to access the unix socket to communicate with the engine.
As a temporary solution, you can use sudo to run the failed command as root.
However it is recommended to fix the issue by adding the current user to the docker group:
Run this command in your favourite shell and then completely log out of your account and log back in (if in doubt, reboot!):
sudo usermod -a -G docker $USER
After doing that, you should be able to run the command without any issues. Run docker run hello-world as a normal user in order to check if it works. Reboot if the issue still persists.
Logging out and logging back in is required because the group change will not have an effect unless your session is closed