On Dec 28, 2014, at 11:44 AM, Vadim Kimlaychuk <vadim.kimlayc...@elion.ee> 
wrote:

> If you try to pull tag = "0.1.4" like:
> 
> docker pull runseb/cloudstack:0.1.4 
> 
> then you don't have this error. But I am still unable to launch the 
> container. Jetty server generates JAVA error stacktrace.
> 
> It seems maintainer must add latest tag to repository and give more 
> information about how to launch the VM.  It is not clear whether re-strarting 
> mysql and running jetty is optional or required actions?
> 

Yeah, give me couple days and I will fix all of this…

thanks for the feedback.

> Regards,
> 
> Vadim.
> ________________________________________
> From: Outback Dingo [outbackdi...@gmail.com]
> Sent: Thursday, December 25, 2014 1:54
> To: users@cloudstack.apache.org
> Cc: prapul cool
> Subject: Re: Dockerr repo for cloudstack
> 
> On Wed, Dec 24, 2014 at 7:32 PM, sebgoa <run...@gmail.com> wrote:
> 
>> 
>> On Dec 24, 2014, at 6:25 AM, Gopalakrishnan S <go...@assistanz.com> wrote:
>> 
>>> Hi Prapul,
>>> 
>>> You can use the following docker image for your cloudstack.
>>> 
>>> https://registry.hub.docker.com/u/runseb/cloudstack/
>>> 
>> 
>> Other than mine there are 3 or 4 others.
>> 
>> We have a pull request to get a docker file in cloudstack source, so
>> everyone will be able to create a dev environment from it.
>> 
>> I am also working on the best way to package the cloudstack binaries,
>> mysql etc…as containers.
>> 
> 
> 
> i was curious so i tried but im getting
> Pulling repository runseb/cloudstack
> 2014/12/25 10:53:27 Tag latest not found in repository runseb/cloudstack
> 
> 
>> 
>>> Thank You.
>>> Gopalakrishnan.S
>>> 
>>> 
>>> ----- Original Message ----- From: "prapul cool"
>> <prapul_cool2...@yahoo.com.INVALID>
>>> To: <users@cloudstack.apache.org>
>>> Sent: Wednesday, December 24, 2014 10:30 AM
>>> Subject: Dockerr repo for cloudstack
>>> 
>>> 
>>> Hi,
>>> Any Docker repository available for cloudstack? please let me know if
>> repo development is in progress... Thanks,Prapul.Sriram.
>>> 
>>> 
>> 
>> 

Reply via email to