


How to solve the problem that docker is not an internal command
With the development of cloud computing, virtualization technology has attracted more and more attention. As an implementation of lightweight container technology, Docker technology is favored by many developers and server administrators. However, some people may encounter problems such as "docker is not an internal command nor an external command" when using Docker. So, what is the problem? Why does it happen? How to solve?
Source of the problem
Docker is a virtualization technology that can package an application and its dependent software into a container, so that the application can run in different environments without affected. When using Docker, we need to enter some instructions through the command line to manage the container. However, when some people use Docker for the first time, an error message "docker is not an internal or external command" may appear.
This problem is usually caused by the computer not recognizing Docker commands. When we enter a Docker command on the command line, the system will look for the location of the command in the environment variable $PATH. If it cannot be found, an error message "Not an internal command" will appear.
Solution
By adding the path
To solve this problem, the easiest way is to add the path of Docker to the environment variable $PATH. This way, the computer can look for Docker commands in this path.
Taking Windows system as an example, you can press the win Pause/Break key combination to open the system properties panel, and then select "Advanced System Settings". In the Advanced tab, select Environment Variables. Find $PATH in "System Variables" (if it is not found, you need to create a new one), and then add the Docker installation path to the end of the variable value. Generally, the installation path of Docker is C:\Program Files\Docker\Docker\resources\bin. After adding, you need to log out and log in again to the system to take effect.
By setting environment variables
Another method is to create a new variable in the environment variable and use the Docker installation path as the variable value. Taking the Linux system as an example, you can open a terminal and enter the command sudo gedit /etc/environment. Create a new variable in the opened file with the name PATH_TO_DOCKER and the value is the installation path of Docker.
LANG=en_US.UTF-8
LC_ALL=en_US.UTF-8
PATH="$PATH:/usr/local/bin:/usr/sbin:/usr/bin:/ sbin:/bin:/usr/games"
PATH_TO_DOCKER="/usr/bin/docker"
Save and exit the file, then enter source /etc/environment in the terminal to make the variables effective immediately.
By reinstalling
If the above two solutions cannot solve the problem, then it may be because Docker is not installed properly. In this case, we can try to uninstall Docker and reinstall it. For specific methods, please refer to Docker official documentation.
Conclusion
Docker is a virtualization technology widely used in cloud computing, containerization and other fields. When we find the problem "docker is not an internal command or an external command" when using Docker, it can be solved by adding a path, setting environment variables, or reinstalling Docker. At the same time, we also need to pay attention to following the correct operating procedures when using Docker to avoid other problems.
The above is the detailed content of How to solve the problem that docker is not an internal command. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











Four ways to exit Docker container: Use Ctrl D in the container terminal Enter exit command in the container terminal Use docker stop <container_name> Command Use docker kill <container_name> command in the host terminal (force exit)

Docker container startup steps: Pull the container image: Run "docker pull [mirror name]". Create a container: Use "docker create [options] [mirror name] [commands and parameters]". Start the container: Execute "docker start [Container name or ID]". Check container status: Verify that the container is running with "docker ps".

Methods for copying files to external hosts in Docker: Use the docker cp command: Execute docker cp [Options] <Container Path> <Host Path>. Using data volumes: Create a directory on the host, and use the -v parameter to mount the directory into the container when creating the container to achieve bidirectional file synchronization.

You can query the Docker container name by following the steps: List all containers (docker ps). Filter the container list (using the grep command). Gets the container name (located in the "NAMES" column).

How to restart the Docker container: get the container ID (docker ps); stop the container (docker stop <container_id>); start the container (docker start <container_id>); verify that the restart is successful (docker ps). Other methods: Docker Compose (docker-compose restart) or Docker API (see Docker documentation).

The process of starting MySQL in Docker consists of the following steps: Pull the MySQL image to create and start the container, set the root user password, and map the port verification connection Create the database and the user grants all permissions to the database

Create a container in Docker: 1. Pull the image: docker pull [mirror name] 2. Create a container: docker run [Options] [mirror name] [Command] 3. Start the container: docker start [Container name]

The methods to view Docker logs include: using the docker logs command, for example: docker logs CONTAINER_NAME Use the docker exec command to run /bin/sh and view the log file, for example: docker exec -it CONTAINER_NAME /bin/sh ; cat /var/log/CONTAINER_NAME.log Use the docker-compose logs command of Docker Compose, for example: docker-compose -f docker-com
