Skip to content
This repository has been archived by the owner on Jun 11, 2021. It is now read-only.

Unable to change volume #2738

Closed
djsowa opened this issue Jun 14, 2017 · 3 comments
Closed

Unable to change volume #2738

djsowa opened this issue Jun 14, 2017 · 3 comments

Comments

@djsowa
Copy link

djsowa commented Jun 14, 2017

Expected behavior

Allow to change volumes for docker image

Actual behavior

When trying to change the volume for mongo image I'm receiving an error:
Invalid directory - Please make sure directory exists and you can read/write to it

Information about the Issue

Kitematic(windows 8.1)

Steps to reproduce the behavior

  1. ...Run mongo image
  2. ...In image settings try to change the volume for /data/configdb
@FrenchBen
Copy link
Contributor

Using toolbox, only your home user folder is shared with the VM. If a different location is selected, you will not be able to use that folder with a folder.

@Mokolos
Copy link

Mokolos commented Oct 4, 2018

thanks a lot (y)

@Nishnha
Copy link

Nishnha commented Mar 11, 2020

In case anyone stumbles upon this answer, there is a workaround for Docker Toolbox on Windows. Normally, Docker Toolbox only provides volumes access to the user's home folder (e.g., C:/Users) and subdirectories.

The workaround is to add a shared folder to the Docker Virtualbox VM with the folder path as the folder you want to share and the mount point as where you want to access it in your Docker Compose file (see the image as reference).

A folder in my external hard drive's project folder with the mount point set to /aifi

You can then access this shared folder by referencing the mount point. For example, my Compose file has:

volumes:
      - "/aifi/data/downloads:/app/data/downloads"

and I can access the files correctly.

Unfortunately, Kitematic does not correctly show the volume and it cannot be set in the program. It gives the same error as OP, Invalid directory - Please make sure directory exists and you can read/write to it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants