Closed carsonbird closed 6 months ago
Alright, I found the issue. Just a typo in the Memcache(d)(?) environment configs. The service and the product are called memcached
with a 'd', but the name of the user directory in the memcached
image is memcache
without a 'd', so... the lines should be
services:
cache:
environment:
SASL_CONF_PATH: /home/memcache/memcached.conf
MEMCACHED_SASL_PWDB: /home/memcache/memcached-sasl-db
OOOOhhhh, maybe it's like "memcache-d", as in "containerd" and "systemd". Maybe the 'd' is for daemon.
I'm getting the following error when attempting to run my own Docker Compose. Everything else about the stack seems to be working fine, and it's a setup I've used extensively in other areas with success, and I'm pretty familiar with it. I'm not sure where the issue would be. Maybe with folder permissions?
So I run
docker compose up
and there aren't any relevant errors (I believe) other than:I have no idea what it's talking about. The Memecached service doesn't have any volumes, and I assume that the
/home/memcached
directory thatmemcached.conf
sits in exists by default in the Memcached docker image, so it should exist.Any ideas what's going on? I can't find any similar errors elsewhere. My files are below.
docker-compose.yaml
.env.example