Skip to content

Too many docker volumes? #44

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

Closed
amchelmer opened this issue Jul 13, 2017 · 5 comments
Closed

Too many docker volumes? #44

amchelmer opened this issue Jul 13, 2017 · 5 comments
Labels

Comments

@amchelmer
Copy link
Contributor

Running docker-compose up starts a total of 5 docker volumes, where two are unnamed. It seems they are used for uploads and storage-uploads, whilst dockerbookstack_storage-uploads and dockerbookstack_uploads remain empty when uploading images in Bookstack.

git clone https://github.com/solidnerd/docker-bookstack.git
cd docker-bookstack/
docker-compose up -d
docker volume ls

returns

DRIVER              VOLUME NAME
local               a6b65c0d08570639759ee0b4ed4dec7356dd41391de7f234e436b9f25e808f52
local               de5deb5b13d07c70f23a52a20737f806950b10c4c33ada5e533e053a4c26da33
local               dockerbookstack_mysql-data
local               dockerbookstack_storage-uploads
local               dockerbookstack_uploads
@vladime
Copy link

vladime commented Aug 4, 2017

I would also like this bug to be fixed.

@vladime
Copy link

vladime commented Aug 7, 2017

@amchelmer Alex, I have managed get rid of one unnamed volume. In docker-compose.yml file you need to change following rows:
volumes: - uploads:/var/www/BookStack/public/uploads - storage-uploads:/var/www/BookStack/storage/uploads
to
volumes: - uploads:/var/www/bookstack/public/uploads - storage-uploads:/var/www/bookstack/storage/uploads

@amchelmer
Copy link
Contributor Author

Good call @vladime. Managed to find the other typo as well. Have submitted a PR.

@solidnerd
Copy link
Owner

Hey,

it will be available in the next release. (0.17.3)

@stale
Copy link

stale bot commented May 10, 2020

This issue has been automatically marked as stale because it has not had any activity for the last 30 days. It will be closed if no further activity occurs during the next 7 days. Thank you for your contributions.

@stale stale bot added the stale label May 10, 2020
@stale stale bot closed this as completed May 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants