1 min read

My little pterodactyl / minecraft / docker problems sheet

I am setting up a Pterodactyl server for a buddy, with a minecraft server on and a few extra goodies (prometheus exporter for minecraft metrics, overviewer for mapping). I've done this a couple times, thought it would be easy enough, however that was not the case.

Invalid mount / config type for "bind"

This one had me stumped. It really did.

  1. Directory did exist
  2. It was owned by pterodactyl, which root can access, even as pterodactyl user trying to create the mount it fails
  3. I thought maybe it's a red herring and it could not mount my worlds directory, from /opt/minecraft
Unable to run a server/ invalid mount config for type “bind”: bind source path does not exist · Issue #4390 · pterodactyl/panel
Current Behavior When I try to start a server, it gives me back this error: container@pterodactyl~ Error Event [e9b132b2-b1ff-418e-99d3-cc977720058d]: environment/docker: failed to create container...

Docker was installed as a snap, I don't remember doing this but it's my friends server so :shrug:

Anyway, install the non-snap docker (I hate snaps) and all is fine.

Wings: "Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?"

It is running! Turns out that there are 2 things to look for here.

  1. systemctl enable --now docker containerd
    Enable docker and the container d
  2. systemctl restart docker.socket
    Make sure you stop and start docker.socket which is managed by systemd separately.