![]() Docker is very helpful on my local machine to support the entire ecosystem of application services. I am using Docker as a tool for my web development environment. There are several configuration to write in the Docker container docker-compose.yml setup for connecting PostgreSQL into the PGAdmin 4 Administration. ![]() As for the purpose of this post and demonstration I am using PgAdmin version 4. PgAdmin may be used on Linux, Unix, macOS and Windows to manage PostgreSQL and EDB Advanced Server 10 and above. But for this post we are going to use and download it in the background with docker container.įor using PostgreSQL in your local computer, we need tools for the databases administration.ĭatabase administration in PostgreSQL using PgAdmin is a popular and feature rich Open Source administration and development platform for PostgreSQL, the most advanced Open Source database in the world. To use PosgreSQL in your desktop you can download it in their website. Only if its not placing your system at risk - consider restarting the server.PostgreSQL is a great and powerfull free open-source RDBMS database system with SQL compliance for any enterprise application. If the service is not critical - you can stop and disable the service. In our case we can see that the process probably is a daemon (PPID is 1) - In that case consider running:Ī) $ cat /proc//status in order to get a more in-depth information about the process like the number of threads spawned by the process, its capabilities, etc'.ī) $ systemctl status in order to see the systemd unit that caused the creation of a specific process. You can also run: $ pstree -s to a visual display of the process and its related processes (install with: brew install pstree). PPID PID PGID SID TTY TPGID STAT UID TIME COMMANDġ 915 915 915 ? -1 Ssl 123 0:11 /usr/bin/redis-server 127.0.0.1:6379Īnd see the ID of the parent process ( PPID) and the execution command. So, In case of the output above the PID is 915. (*) You can also use the lsof command which is mainly used to retrieve information about files that are opened by various processes (I suggest running netstat before that). (*) Because you're not under the scope of the origin compose environment - it is a good practice first to use docker inspect to gather more information about the container that you're about to stop.ģ) Check if port is used by other processes running on the hostįor example if the port is 6379 run: $ sudo netstat -ltnp | grep ':6379' If you find the port is in use by another container, you can stop it with docker stop. ![]() Run docker ps to see list of all containers running under your host. If port is in use by another container, stop it with docker-compose stop or remove it by replacing stop with rm.Ģ) Check the containers running outside your current workspace ![]() In some cases it is critical to perform a more in-depth debugging to the problem before stopping or killing the container/process.ġ) Check you current docker compose environment
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |