Can't add file /root/.pm2/pub.sock to tar: archive/tar: sockets not supported

这个错误是因为 tar 命令不支持打包 socket 文件，所以在打包过程中会出现这个错误。你可以尝试使用 `--exclude` 参数来排除掉该文件，例如：

tar -czvf archive.tar.gz --exclude=/root/.pm2/pub.sock /path/to/archive

这样就可以将 `/path/to/archive` 目录打包成 `archive.tar.gz`，并排除掉 `/root/.pm2/pub.sock` 文件。

相关问题

docker:Can t connect to local MySQL server through socket /tmp/mysql.sock (2)

这个错误通常表示 Docker 容器中的 MySQL 无法连接到本地的 MySQL 服务器。有几种可能的原因和解决方法：

1. 检查 MySQL 服务器是否正常运行。可以尝试在本地终端或命令提示符中连接到 MySQL 并确认它是否运行。

2. 确保在 Docker 容器中正确设置了 MySQL 的主机和端口。可以查看 Docker Compose 文件或 Dockerfile 来确认 MySQL 容器的配置是否正确。

3. 检查容器内 MySQL 的配置文件。通常，MySQL 容器会将 MySQL 的配置文件挂载到容器中。确保配置文件中的套接字路径是正确的，比如 "/tmp/mysql.sock"。

4. 如果正在使用自定义的 Docker 网络或链接多个容器，确保容器之间的网络配置正确，并且 MySQL 容器可以与其他容器或主机进行通信。

5. 如果使用了防火墙或安全组，请检查是否允许 Docker 容器与本地 MySQL 服务器之间的通信。

如果以上方法都没有解决问题，可以提供更多关于你的环境和配置的信息，这样我才能给出更具体的帮助。

: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)

This error message usually occurs when the MySQL server is not running or is not configured correctly. Here are a few steps you can try to resolve the issue:

1. Verify if the MySQL server is running: You can use the following command to check the status of the MySQL service:

   systemctl status mysql

If it's not running, start the service using:

   sudo systemctl start mysql

2. Check the MySQL configuration file: Open the MySQL configuration file (usually located at `/etc/mysql/mysql.conf.d/mysqld.cnf`) and look for the line that specifies the socket file. It should be something like `socket=/tmp/mysql.sock`. Make sure the path to the socket file is correct.

3. Check if the socket file exists: Run the following command to check if the socket file exists:

   ls /tmp/mysql.sock

If it doesn't exist, it means that the MySQL server is not creating the socket file properly. In that case, you may need to reinstall MySQL or check the server logs for any errors.

4. Restart the MySQL service: After making any changes to the configuration file, restart the MySQL service using the following command:

   sudo systemctl restart mysql

If none of these steps work, it's recommended to consult the MySQL documentation or seek help from a database administrator to further troubleshoot the issue.