From HTTP 201 to Persistent Docker Data: Nicola’s MyZubster Pilot Works Locally

Description and use

MyZubster MVP reliably preserves data across container restarts and full Docker Compose shutdowns, proving persistent storage on Windows.

Problem

Ensuring that a Dockerized application preserves data across container restarts and full shutdowns on a local Windows machine.

Outcome

The MyZubster MVP Docker setup successfully preserved observation data across container restarts and full Compose shutdowns, demonstrating reliable persistence on a Windows host.

Workflow

• Clone the repo
• Start Docker Desktop and ensure the Linux engine is running
• Run docker compose up --build -d to build and start services
• Verify API is reachable via http://localhost:5000/api/observations
• Create an observation with a POST request
• Retrieve observations to confirm creation
• Restart the API service with docker compose restart api and verify data persists
• Shut down Compose with docker compose down and check that the volume remains
• Recreate the environment with docker compose up -d and confirm data is still present

Evidence

We recreated the network and container: docker compose up -d

Source

The observation survived the container restart.

Source

The container exited with code 137.

Source