You are using it wrong. Containers should not be permanent things. To keep the container disposable, if there is a problem, it should be removed by rm, the data should be saved outside the container, and then the new container should be run directly. Parameter modifications were made at that time.
In addition, you should use DNS. If it is an internal machine, you can also use internal DNS instead of hard-coding the IP.
Both of these approaches have problems. As for modifying the configuration within the container, this is not recommended. The container is not a virtual machine, and the configuration within it should not be modified.
Look at the priority of environment variables and change the environment variables.
I’m not sure about the priority of environment variables. You can try to set environment variables by starting files like ~/.bashrc ~./.profile in the user directory
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
You are using it wrong. Containers should not be permanent things. To keep the container disposable, if there is a problem, it should be removed by rm, the data should be saved outside the container, and then the new container should be run directly. Parameter modifications were made at that time.
In addition, you should use DNS. If it is an internal machine, you can also use internal DNS instead of hard-coding the IP.
Both of these approaches have problems. As for modifying the configuration within the container, this is not recommended. The container is not a virtual machine, and the configuration within it should not be modified.
Are you using environment variables?
Look at the priority of environment variables and change the environment variables.
I’m not sure about the priority of environment variables. You can try to set environment variables by starting files like ~/.bashrc ~./.profile in the user directory
Have you solved it bro? I have the same problem