)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":15197,"name":"Pierre Riteau","email":"pierre@stackhpc.com","username":"priteau","status":"StackHPC"},"change_message_id":"2945a4ab3bd2c7ee2abb286d896cafd246f844a4","unresolved":false,"context_lines":[{"line_number":7,"context_line":"Make docker registry volume configurable"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"One use case is to use seperate disk for the registry storage. This"},{"line_number":10,"context_line":"can prevent the rootfs from filling up."},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"Change-Id: I9634ee7f5730e93b8ddd96de04982d638dd4dae2"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3fa7e38b_a3326d0d","line":10,"range":{"start_line":10,"start_character":16,"end_line":10,"end_character":22},"updated":"2020-02-19 10:38:14.000000000","message":"This would only be possible if using an overlay driver, right? By default the seed uses the devicemapper storage driver, storing data in the docker-thinpool LV.","commit_id":"06ad1c3a96f433b7e890d7141a3bcafe6743d383"},{"author":{"_account_id":15197,"name":"Pierre Riteau","email":"pierre@stackhpc.com","username":"priteau","status":"StackHPC"},"change_message_id":"0c8ad9ca4e7a2394673237fb6987dc30be774518","unresolved":false,"context_lines":[{"line_number":7,"context_line":"Make docker registry volume configurable"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"One use case is to use seperate disk for the registry storage. This"},{"line_number":10,"context_line":"can prevent the rootfs from filling up."},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"Change-Id: I9634ee7f5730e93b8ddd96de04982d638dd4dae2"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"1fa4df85_6f2a3ce8","line":10,"range":{"start_line":10,"start_character":16,"end_line":10,"end_character":22},"in_reply_to":"1fa4df85_2f83e406","updated":"2020-02-24 10:49:34.000000000","message":"Without this patch, images pushed to the registry end up being stored inside the container layer, right? My comment was meant to say that this wouldn\u0027t fill the host rootfs if devicemapper was in use.\n\nI guess Will may have been referring to the rootfs of the container, which could be a concern as well. Maybe more importantly: without the volume added by this patch, you would lose all your images if you destroyed the container?","commit_id":"06ad1c3a96f433b7e890d7141a3bcafe6743d383"},{"author":{"_account_id":14826,"name":"Mark Goddard","email":"markgoddard86@gmail.com","username":"mgoddard"},"change_message_id":"65b3f6ec51ab4c6a32394a64f0eeb6f72529dfdf","unresolved":false,"context_lines":[{"line_number":7,"context_line":"Make docker registry volume configurable"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"One use case is to use seperate disk for the registry storage. This"},{"line_number":10,"context_line":"can prevent the rootfs from filling up."},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"Change-Id: I9634ee7f5730e93b8ddd96de04982d638dd4dae2"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"1fa4df85_8ff4585d","line":10,"range":{"start_line":10,"start_character":16,"end_line":10,"end_character":22},"in_reply_to":"1fa4df85_6f2a3ce8","updated":"2020-02-24 10:59:46.000000000","message":"Will hasn\u0027t changed the default behaviour here - images are stored in a named volume called docker_registry. This patch allows the volume name to be changed, or set to a path for a bind mount.","commit_id":"06ad1c3a96f433b7e890d7141a3bcafe6743d383"},{"author":{"_account_id":14826,"name":"Mark Goddard","email":"markgoddard86@gmail.com","username":"mgoddard"},"change_message_id":"881a6d385c4c3388f7bb9ef8c57fa35002caa209","unresolved":false,"context_lines":[{"line_number":7,"context_line":"Make docker registry volume configurable"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"One use case is to use seperate disk for the registry storage. This"},{"line_number":10,"context_line":"can prevent the rootfs from filling up."},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"Change-Id: I9634ee7f5730e93b8ddd96de04982d638dd4dae2"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"1fa4df85_2f83e406","line":10,"range":{"start_line":10,"start_character":16,"end_line":10,"end_character":22},"in_reply_to":"3fa7e38b_a3326d0d","updated":"2020-02-24 10:42:35.000000000","message":"Data in volumes does not use the storage driver - it\u0027s just a bind mount.","commit_id":"06ad1c3a96f433b7e890d7141a3bcafe6743d383"}],"releasenotes/notes/add-variable-docker-registry-datadir-volume-a5ec931a5eb2c59d.yaml":[{"author":{"_account_id":17669,"name":"Doug Szumski","email":"doug@stackhpc.com","username":"DougSzumski"},"change_message_id":"f8fa9955f1419502cc09d34e5e74cbf0ee789825","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"features:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    Adds the variable, ``docker_registry_datadir_volume``. This allows you to"},{"line_number":5,"context_line":"    configure the name or path of the docker volume used for the docker registry."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1fa4df85_2f1ccebf","line":4,"updated":"2020-03-19 09:55:43.000000000","message":"I did this by overriding `docker_registry_services`, but this is neater.","commit_id":"06ad1c3a96f433b7e890d7141a3bcafe6743d383"}]}