You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I set memcached -m 256 as command (not entrypoint), then things properly work. And it seems more correct to run the container with the original entrypoint as it may involve a custom init or who knows what.
While I'm using podman, there might be some difference (although I doubt it). I can't test it with stock docker-compose.
Hello, the memcached image doesn't start with this entrypoint for me. It fails with
Inspecting the image shows
When I set
memcached -m 256
ascommand
(notentrypoint
), then things properly work. And it seems more correct to run the container with the original entrypoint as it may involve a custom init or who knows what.While I'm using podman, there might be some difference (although I doubt it). I can't test it with stock docker-compose.
https://github.com/haiwen/seafile-admin-docs/blame/3d7db2f981021b7446a0384915797161e3de824e/manual/docker/docker-compose/ce/11.0/docker-compose.yml#L17
The text was updated successfully, but these errors were encountered: