Stopping containers removes volumes #10769

2 Answer(s)

• 

  0

  AI-Bot created 2 months ago

  Support Team ABP Agent

  • ABP Studio stops Docker containers by executing docker-compose down (see the ABP Studio MCP “Container Control” notes). In Docker Compose, volumes are only removed if down is executed with -v/--volumes. So, if your volumes are being deleted when you click “Stop All”, ABP Studio is effectively running a “down that removes volumes” for that bulk operation (or running an additional cleanup step after stopping).
  • Workaround (recommended): don’t use “Stop All” for your data-heavy services. Instead, stop containers individually (as you already noticed, volumes remain), or run your own stop script/task that does not remove volumes.

  Make your OpenSearch data survive “Stop All” (robust workaround)

  Convert the named volume to an external volume so Compose (and any down -v) won’t remove it automatically:

  volumes:
    meinwerk_opensearchdata:
      external: true
  

  Then create it once:

  docker volume create meinwerk_opensearchdata
  

  With external: true, Compose treats it as pre-existing infrastructure and won’t delete it as part of down cleanup.

  Also check your own scripts

  Your posted down.ps1 uses plain docker-compose ... down (no -v), which should not remove volumes. So the volume deletion behavior is coming from ABP Studio’s bulk stop behavior (not from your down.ps1 as written). Using the external: true volume avoids data loss regardless.

  (light) Sources

  • https://abp.io/community/articles/ex7r27y8 (ABP Studio docker container management article; explains Studio’s docker integration approach and scripts)

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  maliming created 2 months ago

  Support Team Fullstack Developer

  Hi,

  You're right, this is a bug on our side. When you use "Stop" on the whole Containers group ("Stop All"), ABP Studio brings the containers down with docker compose down -v, and the -v removes the Compose-managed named volumes too. Stopping an individual container doesn't remove the volumes, which is why the volume survives in that case.

  For now, mark the volume as external so Compose won't remove it even on down -v:

  volumes:
    meinwerk_opensearchdata:
      external: true
      name: meinwerk_opensearchdata
  

  Then create it once before running:

  docker volume create meinwerk_opensearchdata
  

  External volumes are treated as pre-existing infrastructure, so down -v leaves them untouched, and your OpenSearch data will persist across "Stop All" from now on. One thing to watch: if your current data is sitting in a project-prefixed volume (e.g. <project>_meinwerk_opensearchdata), point name: to that exact volume instead of creating a new empty one.

  We'll fix this in the next ABP Studio release so "Stop All" keeps the volumes just like stopping a single container does.

  Thanks

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel