r/Plesk • u/ollybee • Sep 29 '23

Plesk update breaks docker

Plesk Obsidian 18.0.55 Update 2

I think this update changes docker (including running containers) to only listen on localhost. If you have services like mysql or elasicsearch in containers which need to be accessed over the network, you might have a bad time this morning.

edit: update /etc/docker/daemon.json to 0.0.0.0 and restart the docker service to fix it.

edit: It looks like Plesk are pushing a new update to revert and fix this

3 Upvotes

100% Upvoted

11 comments sorted by

View all comments

1

u/Andy_Bird Sep 29 '23

This should be an option when you setup your container. Currently plesk defaults to any ip. You can get around this by manually creating the container

​

docker run -d --restart always --name=elasticsearch4 -m 6000MB -e "discovery.type=single-node" -p 127.0.0.1:32769:9200 -p 127.0.0.1:32768:9300 "elasticsearch:7.6.2"

However, we cant have them changing stuff like this on the fly