Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker volume warning shows when using Docker named volumes #3885

Open
1 task done
andrewvaughan opened this issue Jun 27, 2024 · 3 comments
Open
1 task done

Docker volume warning shows when using Docker named volumes #3885

andrewvaughan opened this issue Jun 27, 2024 · 3 comments

Comments

@andrewvaughan
Copy link

Description

When using a named volume (e.g., this in Docker Compose):

    #....
    volumes:
      - "overseerr-config:/app/config"
    
volumes:
  overseer-config:

The app still shows the message:

The /app/config volume mount was not configured properly. All data will be cleared when the container is stopped or restarted.

This is not true, as named volumes are persisted in /var/lib/docker and are simply managed by Docker (or Compose).

Version

1.33.2

Steps to Reproduce

  1. Create a volume with docker volume create ...
  2. Mount that named volume to Overseerr during Docker setup

Screenshots

No response

Logs

No response

Platform

desktop

Device

Server

Operating System

Ubuntu

Browser

All

Additional Context

No response

Code of Conduct

  • I agree to follow Overseerr's Code of Conduct
@danshilm
Copy link
Collaborator

There's no reliable way afaik to detect that a folder has been bind mounted correctly.
There's a notice in the Windows installation section, and probably also has to be included in the Linux installation section on the docs.

@regg00
Copy link

regg00 commented Nov 28, 2024

Indeed the notice should be included in the Linux section of the documentation.

Copy link

stale bot commented Jan 31, 2025

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants