Skip to content
This repository has been archived by the owner on Jul 19, 2019. It is now read-only.

impossible to launch several containers of the same project at once #5

Open
rvalyi opened this issue Sep 4, 2014 · 5 comments
Open
Labels

Comments

@rvalyi
Copy link
Member

rvalyi commented Sep 4, 2014

there is the port clash which would be easy to fix by offsetting things.

there is a name clash as the container is named after the folder name. We should eventually test if there is such docker container and if so increment some counter.

finally is that going to work to have 2 instance of a Postgresql server using the same data dir? I would say yes, but that's worth checking.

@fgrehm
Copy link

fgrehm commented Sep 5, 2014

finally is that going to work to have 2 instance of a Postgresql server using the same data dir? I would say yes, but that's worth checking.

I remember trying that out and it didn't work, but please tell me if you are able to do that

@rvalyi
Copy link
Member Author

rvalyi commented Sep 5, 2014

Hey, hello Fabio.

That's amazing I just tried over the last hour and came to the same conclusion: it's talking about CRITICAL flush errors in the Postgresql log.
Too bad, I'll have to prevent creating 2 containers of the same project again. Unless I try to inject the Postgresql of the 1st container into the 2nd with --link but as for me this is too much hassle for too little benefit.

BTW, I just started basing my image on your official devstep image now (I as using a fork before you released 0.1.0)

@fgrehm
Copy link

fgrehm commented Sep 5, 2014

One option would be to manage a separate postgres container and always use --links + Devstep's default port forwarding, but I understand you want to keep things simpler and avoid using multiple containers.

@rvalyi
Copy link
Member Author

rvalyi commented Sep 5, 2014

Yes, in my use case the benefit of simplicity largely outweighs the impossibility to have 2 containers.

I don't know if that's a use case you see for Devstep. But as I said, I see a use case embedding it in Vagrant for the disabled part of the humanity. Unless I see strong signals Vagrant start managing the whole Docker cycles flawlessly, I prefer a single container.

Also, I personally see room to use Postgresql just like Sqlite here. But again, this may be the specificity of the project I deal with that won't work with Sqlite while standard projects tend to use decent ORM's that work with Sqlite for development...

@fgrehm
Copy link

fgrehm commented Sep 12, 2014

Just so you know, the support for running commands on an existing container might land in docker soon, there is a PR open for that and it is likely that it'll make things easier for you ;-)

@rvalyi rvalyi added the wontfix label Nov 15, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants