Causes: accidentally use kill -9 to delete the Podman container running java program process, start the container again with an error

Description of the problem: The problem is because the port is occupied, can not start

Solution: This is because the port is occupied, you can only find out which process is occupying the port through netstat (I am showing the PID/slirp4netns ), and then kill the process number of the occupied port PID with kill -9

Read More:

• Setting up automatic networking alias for Mac Terminal
• [Solved] Web server failed to start. Port 8080 was already in use.
• [Solved] Bash: Syntax error: redirection unexpected
• Aliyunshield occupies port 80 error: Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use
• linux tomcat Run (DWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [debugIni）
• Linux gets the program PID according to the port
• Gamit Run Error: grep SP file :bad year 2021 [How to Solve]
• [Solved] Linux Error: Failed to start bean ‘webServerStartStop‘; nested exception is org.springframework.
• Git error bad signature [How to Solve]
• Notes on Linux SCP command using specific port
• [Solved] Failed to start LSB: Bring up/down networking
• How to Add Dfrours Model
• Linux solves nohup: ignoring input and appending output to “nohup. Out” and nohup: ignoring input redirection error to standard output
• [Solved] Linux SSH Login Terminal Error: shell request failed on channel 0
• [Nginx] solution: it can’t be accessed on the background API interface after HTTPS (access the specified port through the domain name)
• [Solved] Virtual machine Failed to restart network Error: Error:Failed to start LSB: Bring up/down networking
• Termux setting path environment variable
• SSH Connect Service Error: Could not connect to ‘xxx.xxx.xx.xx‘ (port 22): Connection failed.
• [Solved] FATAL CONFIG FILE ERROR: Bad directive or wrong number of arguments
• CentOS7 Failed to start LSB: Bring up/down networking [How to Solve]