Bird
0
0

After restoring a volume from a backup tarball, you notice the container cannot access the data. What is a common cause?

medium📝 Troubleshoot Q7 of 15
Docker - Production Patterns
After restoring a volume from a backup tarball, you notice the container cannot access the data. What is a common cause?
ADocker daemon needs restart after restore
BThe volume was not recreated before restore
CFile ownership and permissions were not preserved during restore
DThe backup tarball was corrupted
Step-by-Step Solution
Solution:

  1. Step 1: Consider file permissions impact

    If file ownership or permissions are lost during restore, containers may lack access rights.

  2. Step 2: Check restore method

    Using tar without preserving ownership (-p flag) can cause permission issues.

  3. Final Answer:

    File ownership and permissions were not preserved during restore -> Option C

  4. Quick Check:

    Permissions affect container data access [OK]
Quick Trick: Preserve permissions when restoring backups with tar -p [OK]
Common Mistakes:
  • Assuming volume recreation fixes permissions
  • Blaming Docker daemon restart unnecessarily
  • Ignoring backup file integrity checks

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Docker Quizzes
Docker Security - Read-only filesystem containers - Quiz 7medium Docker Swarm - Overlay networks in Swarm - Quiz 6medium Docker in CI/CD - Docker layer caching in CI - Quiz 10hard Docker in CI/CD - Pushing images from CI - Quiz 11easy Image Optimization - Scratch base image for minimal containers - Quiz 12easy Logging and Monitoring - Alert setup for container health - Quiz 8hard Production Patterns - Container orchestration in production - Quiz 7medium Production Patterns - Canary deployment pattern - Quiz 9hard Resource Management - CPU limits and reservations - Quiz 6medium Resource Management - Why resource limits matter - Quiz 11easy