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

Adding a volume to an existing kitematic container ? #1923

Closed
sgentile opened this issue Aug 20, 2016 · 37 comments
Closed

Adding a volume to an existing kitematic container ? #1923

sgentile opened this issue Aug 20, 2016 · 37 comments

Comments

@sgentile
Copy link

sgentile commented Aug 20, 2016

Most every example showing volumes starts from an image via command line. How do I add a volume share to an existing kitematic container ?

(I have Docker Kitematic 0.12.0)

@sgentile
Copy link
Author

And to add, the documentation images showed here https://kitematic.com/docs/managing-volumes/ do not match what I'm seeing - (I'm running Docker on Mac)

@FrenchBen
Copy link
Contributor

What you're seeing is images that properly declare the volume that they allow user to map - Unfortunately not images are made equally, which results in no volume mapping shown.

For Kitematic to display the option, the image needs to have a VOLUME entry. Some early work was done to allow none-exposed volumes to work, but it hasn't been touched in a while:
#1202

@aaomidi
Copy link

aaomidi commented Oct 1, 2017

This... makes no sense.

You don't have to have a VOLUME in the Dockerfile to work with mapping diskspace.

Give people the option to do host mapping of disks regardless of there being VOLUME or not.

@stereokai
Copy link

stereokai commented Jan 21, 2018

@FrenchBen So why is this closed? It's still an issue.
@jmorganca @seanli

@Dgc2002
Copy link

Dgc2002 commented Feb 20, 2018

@FrenchBen any chance we can get further comment on this? As @aaomidi said this isn't a requirement of docker that I'm aware of, just one that seems arbitrarily enforced here in kitematic.

This was also confusing and frustrating as a newer kitematic user. Under the Hostname/Ports tab I'm able to add port mappings, but under Volumes I'm not able to add volumes. As a docker user I'm expecting to be able to emulate -v in the same way I would -p in this scenario.

Here are the images from the first page of https://hub.docker.com/explore and if they include VOLUME

Image Uses VERSION
alpine NO
nginx NO
httpd NO
redis YES
busybox NO
ubuntu NO
mongo YES
memcached NO
mysql YES
registry YES
postgres YES
Node NO
consul YES
centos NO
hello-world NO

That's 9 NO and 6 YES.

Some other notable images, note the first one:
(chosen by name recognition)

Image Uses VERSION
docker NO
logstash NO
ruby NO
wordpress YES
php NO
mariadb YES
elasticsearch YES
golang NO
python NO
debian NO
java NO
tomcat NO
jenkins YES

That's 9 NO and 4 YES

@incompletude
Copy link

I'm also interested in getting further comments on this. For me, not having a way to add a volume to an apache image defeats the purpose of using Kitematic for dev purposes.

@oblogic7
Copy link

Found Kinematic today and am abandoning it because of this issue. Could not for the life of me figure out why such a simple task was impossible to accomplish. Back to the command line I go.

@sistematico
Copy link

There Is no way to add volumes on existent container using Kitematic? Little lost at this point...

@richard-fairthorne
Copy link

richard-fairthorne commented May 3, 2018

+1 - As a developer, I would like to use local tools to work inside a docker container.

@bemcculley
Copy link

@FrenchBen is there any update on why this issue was closed? Or at least a "we have no plans to support this option" so someone else might pick up the work?

@FrenchBen
Copy link
Contributor

@bemcculley Kitematic detects the VOLUME entry to show the mapping, it's not a question of needing it for mapping to work as @aaomidi alluded to.
There is no functionality in Kitematic to currently map a folder outside of the container to a folder inside of the container.
IF someone wants to pickup the different PRs and make something happen, then it'll be in Kitematic.

It's an OSS project, anyone can contribute and help make it better. :)

@tombuckley91
Copy link

That's a shame - I was looking for this feature as well. I can run the image on the command line and add a volume that way (obviously) but it's pretty poor to not be able to add volumes after the fact. I would love to see this feature supported.

@stereokai
Copy link

@FrenchBen Maybe reopen this issue then? Obviously this is a major problem for a significant part of the community.

@10XL
Copy link

10XL commented Jun 1, 2018

#3692 looks like it fixes this(and #2518) but it's been 2 months since any activity.

@ragaar
Copy link

ragaar commented Jul 19, 2018

You can connect directly to the VM and run the docker commands from inside the VM with a -v flag.

In the settings > volumes tab I have access to [CHANGE] the local folder.

I confirmed the container will populate the folder with settings, although in my particular case I'm debugging why it fails to start. There may be some additional restrictions (aside from the /c/Users/). 🔮

@LiamKarlMitchell
Copy link

Reopen, being able to add volume mappings from the UI should be a standard feature.
Also should be able to choose any location to mount in on Windows host.

@Marahin
Copy link

Marahin commented Oct 1, 2018

Signed, this feature would be very nice!

@leksa
Copy link

leksa commented Oct 16, 2018

Love to see the fix for volume map in Kitematic

@rsunmoto
Copy link

rsunmoto commented Nov 5, 2018

+1

2 similar comments
@saintz666
Copy link

+1

@SergioSuarezDev
Copy link

+1

@jadertao
Copy link

same

@evandrix
Copy link

👍 any alternatives/existing workarounds for now, though?

@stereokai
Copy link

stereokai commented Dec 17, 2018

I opened a new issue to try and raise awareness. Please thumb up here: #4399

@aaomidi
Copy link

aaomidi commented Dec 17, 2018

Wrote a pull request at #4401. Hopefully now there isn't an excuse to not do this :)

@novalex
Copy link

novalex commented Mar 26, 2019

Thanks @droidmahn , portainer works great. I was able to add more volumes to my existing containers, and it handled recreating and restarting them automatically, without any issue. It also has lots of options for the containers and other great stuff, like creating images and stacks. It doesn't seem to like Kitematic's container linking though, and it shows containers which are linked to from other containers as "linked_name:name".

@bartclaeys
Copy link

I am new to Docker, decided going the route of Kitematic and now discovering the volume setting is not always exposed?

@aaomidi
Copy link

aaomidi commented Apr 8, 2019

@bartclaeys I have a PR open that fixes it, until then I recommend avoiding kitematic.

@rorych
Copy link

rorych commented May 5, 2019

Would be awesome to see the fix for volume map in Kitematic! Otherwise the best tool to get started with docker.

@devhero-tech
Copy link

still issue? shieeet

@rorych
Copy link

rorych commented Jul 12, 2019

still issue? shieeet

I would say so.
We changed to DockStation -> https://dockstation.io/

Similar GUI, but project based and more options.
First you will have to start of with a docker-compose File.
But once you have your setup it seems like the "better" tool.

@weboAp
Copy link

weboAp commented Jul 19, 2019

a workaround that worked for me is to create a symlic from the c:\Users\user.myprojects to d:\myprojects
mklink /J c:\Users\user \ .myprojects d:\myprojects
and reference my volumes that way.

@UnMatty
Copy link

UnMatty commented Oct 4, 2019

Still have a problem on my mac

@dstibbe
Copy link

dstibbe commented Nov 18, 2019

What kind of joke is this? The point of this GUI is so I don't have to use -v on the command line.

@richlysakowski
Copy link

Docker is not responding to its real user community. According to this post alone, this missed requirement has been an Gaping Requirement Open Sore Systems software (GROSS) for 3.5 years. This NEEDS to be a CORE feature of the CORE Docker product. This missed requirement is like in "the marketing idiot old days" of 2000 when Documentum had only an API for its "Users" (aka programmers), and the Documentum Desktop was created as a "demo" for a particular customer to illustrate how to use the "product". Other customers found out about it and insisted on having the demo source code with their purchase. It took Documentum many years to create a "Whole Product" offering, by which time their document management software competition had passed them by. What Fools be Docker Marketing???? Are they paying attention to their customers' requirements? Obviously not. Or are they only catering to the requirements of their surrogate users (their internal developers and marketing staff who used to be Docker developers and now represent the "User Community". Surrogate users' are by definition out of touch with the real users of the product. @dstibbe got it right... "What kind of joke is Docker/Kitematic?" GROSS software is unconscionable. Kitematic / Docker ... get your program "with the program" and enable your users.

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