Unfortunately, as an AI language model, I cannot provide a specific solution without additional context. However, “Got permission denied while trying to connect to the Docker daemon socket at uni” error usually occurs when the user doesn’t have the necessary permissions to access the Docker daemon.
You may try the following solutions:
Add your user to the docker group by running
sudo usermod -aG docker <username>and then logout and log back in for the changes to take effect.Run Docker commands with sudo, i.e., prefix the command with ‘sudo’.
Check if the Docker service is running by executing
sudo systemctl status docker.If you’re using Docker Desktop on Windows or macOS, make sure the Docker Desktop application is running.
Sometimes, the issue might be related to file permissions. Check if the files/folders that Docker uses have proper read/write permissions.
If none of the above solutions work, you may need to provide more information about your setup, Docker version, and operating system to get further help.
![[pgsql]
host=127.0.0.1
port=5432
database=emm_manager
user=uniemm
passwd=OPwdVGWjHT8nQmQ7BEav8g==
[redis]
host=10.19.83.70,10.19.83.70,10.19.83.70,10.19.83.70,10.19.83.70,10.19.83.70
port=7001,7002,7003,7004,7005,7006
passwd=8xNnDa3XamGiMw==
mode=...](https://linuxcpp.0voice.com/zb_users/upload/2023/05/202305162237121215388.png)
![sed -i "s/${dbconf_map["java_addr"]}/${shardingsphere_proxy_vip}:${shardingsphere_proxy_port}/g" $java_conf_path 双引号是否会错乱？](https://linuxcpp.0voice.com/zb_users/upload/2023/05/202305162214216277121.png)
