-
-
Notifications
You must be signed in to change notification settings - Fork 543
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memcached process not started once container running #1827
Comments
I can confirm that I am also seeing this in rc22 (also rc21) The hack that @johangant mentioned does seem to allow my app to connect to memcached |
Also seeing this in rc22. Starting This is the output of
I tried starting
|
Starting memcache manually works for me too. |
Looks like there are a lot of issues like this, that something happens with Bitnami and the container does not work anymore with Lando. |
This is a workable
|
Why I didn't come here earlier. Was pulling my hair out with this. Well good thing is I have a bit alternative solution:
I'll add also my Drupal configuration needed to get this work:
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions and please check out this if you are wondering why we auto close issues. |
I'd think this is still worth fixing? |
So it looks like the issue here is that the new When docker tries to mount a non-existent file it usually ends up creating an empty directory instead of the actual file. If you ssh into a memcache container and check out This should be easy to fix by itself. we should also get better tests for memcached so regressions like ths are easier to catch. |
Alright, this is merged into |
Tell us about your setup
Lando version: v3.0.0-rc.22
Operating system: macOS 10.14.6
Tell us about your
.lando.yml
Tell us about the command you were running
Tell us about the error you got
Running the above steps should give you a refused connection from the memcached container which, although reported as healthy, has no running memcached service inside it so refuses connections from applications or other tools.
What I've noticed is that if you run these commands, you can get it to connect:
Tell us generally about your bug
If I run the docker image with
docker exec -it memcached /bin/bash
it has a working memcached process running.I'm a little unclear whether it's the lando helper scripts that might need adjusting or if it's an upstream change that might have caused a fault.
Some output from
lando logs -s memcached
which may be relevant:The text was updated successfully, but these errors were encountered: