It seems that every time I update the docker code file, the uploaded resources disappeared-CSDN博客

本文链接：https://blog.csdn.net/Richardlcx/article/details/130807741

The issue you’re experiencing is a common one when using Docker for application development. When you rebuild your Docker container, all data stored within the container is lost because Docker containers are stateless by design. This means that the video files you upload during one run of your container aren’t present when you stop and start the container again.

There are multiple ways to persist data across Docker container runs. One of the common ways is to use Docker volumes. Docker volumes are the preferred mechanism for persisting data generated by and used by Docker containers. They are completely managed by Docker.

Here’s how you could use Docker volumes to store your uploaded video
files:

Create a Docker volume. You can do this with the following command:
```
docker volume create myvideostorage
```
Mount this volume to your container. When you run your container, you’d add the -v option to your docker run command:
```
docker run -v myvideostorage:/path/in/container -p 5000:5000 your-flask-image
```

Replace /path/in/container with the path where you’d like to store your video files within the container (for example, the path could be /app/uploads).

With this approach, even if you rebuild your container, the uploaded videos are stored in the Docker volume and can be accessed by the application. Make sure to update the UPLOAD_FOLDER configuration in your Flask application to point to the directory where you mount your Docker volume in the container.

You typically specify volumes in your Docker run command, not in your Dockerfile. However, you can specify a volume in a Dockerfile using the VOLUME instruction. But this volume will be created with a random name when a container is built from the Dockerfile.

A more preferred way is using docker-compose, which is a tool for defining and managing multi-container Docker applications.

Here’s a basic docker-compose.yml file that specifies a volume:

version: '3'

services:
  app:
    build: .
    ports:
      - "5000:5000"
    volumes:
      - myvideostorage:/app/uploads

volumes:
  myvideostorage:

This file defines a single service named app, which is built from the Dockerfile in the current directory (build: .). The service is accessible at localhost:5000, and it has a volume attached to it. The volumes key under app mounts the myvideostorage volume at /app/uploads in the container.

The volumes key at the bottom of the file defines a named volume called myvideostorage. Docker will automatically create this volume when you bring up the Docker Compose application.

To bring up the application, you would use the docker-compose up
command:
```
docker-compose up -d --build
```

This command starts the application in detached mode (-d), and it rebuilds the image before starting the container (–build).

Remember to update your Flask application’s UPLOAD_FOLDER configuration to /app/uploads, the directory where the Docker volume is mounted in the container. With this setup, the uploaded videos will be stored in the myvideostorage Docker volume and persist across container restarts and rebuilds.