Add note about memcached SIGTERM

memcached/README.md

@@ -1,6 +1,6 @@
 # Supported tags and respective `Dockerfile` links
 
-
+- [`1.4.21`, `1.4`, `1`, `latest` (*Dockerfile*)](https://github.com/docker-library/memcached/blob/2abd5c1e975313238af4291264902812a04a1815/Dockerfile)
 
 For more information about this image and its history, please see the [relevant
 manifest file
@@ -38,6 +38,14 @@ variables generated by the link as well as through DNS as `memcache` from
 
 For infomation on configuring your memcached server, see the extensive [wiki](https://code.google.com/p/memcached/wiki/NewStart).
 
+# Known Issues
+
+As of 1.4.21, memcached does not handle `SIGTERM`, so a standard `docker stop`
+will not stop it gracefully, but will resort to `SIGKILL` after the 10 second
+timeout.  Use `docker kill -s INT` to do a clean stop of the memcached
+container.  There is [a PR](https://github.com/memcached/memcached/pull/88) to
+change this behavior upstream.
+
 # License
 
 View [license

memcached/content.md

@@ -27,3 +27,11 @@ variables generated by the link as well as through DNS as `memcache` from
 `/etc/hosts`.
 
 For infomation on configuring your memcached server, see the extensive [wiki](https://code.google.com/p/memcached/wiki/NewStart).
+
+# Known Issues
+
+As of 1.4.21, memcached does not handle `SIGTERM`, so a standard `docker stop`
+will not stop it gracefully, but will resort to `SIGKILL` after the 10 second
+timeout.  Use `docker kill -s INT` to do a clean stop of the memcached
+container.  There is [a PR](https://github.com/memcached/memcached/pull/88) to
+change this behavior upstream.