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

Named Volume Support for Compose Recipes #2783

Closed
JamesDrummond opened this issue Oct 13, 2016 · 4 comments
Closed

Named Volume Support for Compose Recipes #2783

JamesDrummond opened this issue Oct 13, 2016 · 4 comments
Labels
kind/enhancement A feature request - must adhere to the feature request template. status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach

Comments

@JamesDrummond
Copy link
Contributor

Enhancement request for named volumes support in compose recipe. This enhancement will allow runtime machines in a multi-machine workspaces the ability to share folders/files through shared volumes created specifically for the multi-machine workspace while not making the host file system vulnerable.

This enhancement is related to codenvy/codenvy#897.

Expected Usage Example:

services:
  db:
    image: codenvy/mysql
    volumes:
      - db_volume:/mnt/db_volume
    environment:
      MYSQL_DATABASE: petclinic
      MYSQL_USER: petclinic
      MYSQL_PASSWORD: password
    mem_limit: 1073741824
  dev-machine:
    image: codenvy/ubuntu_jdk8
    mem_limit: 2147483648
    volumes:
      - db_volume:/mnt/db_volume
    depends_on:
      - db
  volumes:
    db_volume:

@slemeur slemeur added the kind/enhancement A feature request - must adhere to the feature request template. label Oct 13, 2016
@JamesDrummond JamesDrummond added status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. team/platform labels Nov 7, 2016
@skabashnyuk skabashnyuk added status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach and removed status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Nov 16, 2016
@JamesDrummond
Copy link
Contributor Author

@skabashnyuk Any progress on this yet?

@asthomasdk
Copy link

I am also keen to hear what the status / thoughts are on this one.

Using data volumes is a common (and essential) thing for our Docker setup. We very often create personal stacks which have a database container and also a data container for the database - so that we can easily upgrade the database container without losing any of the user's data.

I cannot see how you can achieve this currently. Unless I am overlooking something ... How are you currently handling databases and data for the databases that needs to be persisted during development ?

@TylerJewell
Copy link

This type of enhancement is a good enhancement. We will let it live here. @JamesDrummond - this would likely not be considered until we complete some of the internal refactorings that we want to do with agents & machine runtimes. Particularly the agent stuff is very cool because we will write a lightweight agent launcher that can launch agents in a workspace in parallel. We are also working on the migration of Factories from Codenvy into Eclipse Che. This is also likely something that would be handled by the same development team that would own evolving the compose syntax and features.

  1. Rework agents installation #3971
  2. Machine API related house keeping #3612

@asthomasdk
Copy link

Sounds good.

With all the work being done with Docker volumes and more and more work being done on supporting distributed data storage for docker - I think this will become increasingly important.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A feature request - must adhere to the feature request template. status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach
Projects
None yet
Development

No branches or pull requests

5 participants