I've been playing with Artemis and docker over the weekend.
I've created images for 1.0.0 and 1.1.0, see vromero/activemq-artemis
<https://hub.docker.com/r/vromero/activemq-artemis/>. If you have docker
installed you can try them with:
docker run -it vromero/activemq-artemis
or
docker run -it vromero/activemq-artemis:1.0.0
Clebert, regarding your point I'm actually taking back what I said before.
After this I realised there is value in helping to shift highly
personalized instances into docker images. I'm afraid I can't share a clear
proposal yet but just my thoughts.
I'm thinking in a base docker image that contains everything but the
instance directory ifself. Then there are a few options:
- Expect the user to *mount* (this is the -v parament in docker) the
instance directory into the image.
- Completely external tool (a docker image itself that can be downloaded
and run in a single command or perhaps even something that can be curl-ed)
or sitting in the instance that creates a dockerfile, that the user could
use to create the image
- Same tool, that creates the actual docker image rather than the
dockerfile (prevents the user to do further customization but its more
straight forward to use).
Personally I lend a bit torwards a docker image that knows how to create
both a dockerfile and a dockerimage from a given instance. The reason is
not to push into the distribution things that doesn't necessarily have to
live there, specially given that the docker toolset have to be installed
anyways. This would perhaps look something like:
docker run --rm -v /mylocalinstance:/instance
activemq/artemis-docker-builder build-image
What do you think? Would perhaps make more sense to have someting in a jar
than can be invoked from bash/cmd?
2015-09-23 15:29 GMT-07:00 Victor Romero <victor.rom...@gmail.com>:
> > but if that was automated through the CLI, maybe it would make it easier
> > for using docker?
>
> If it is just about creating the dockerfile it is definitely feasible but
> it would probably be rather unexpected for users and specially for
> dockerhub if we create CI for an image.
>
> I'll come back with something early next week.
>
> 2015-09-23 14:06 GMT-07:00 Clebert Suconic <clebert.suco...@gmail.com>:
>
>> but if that was automated through the CLI, maybe it would make it easier
>> for using docker?
>>
>>
>> I was thinking of a way to create the docker image along with other
>> parameters passed on the build...
>>
>> but if the only way is the official image.. then I guess that's the way to
>> go... we will need some doc around on how to use docker.
>>
>> On Wed, Sep 23, 2015 at 5:00 PM, Victor Romero <victor.rom...@gmail.com>
>> wrote:
>>
>> > It is too environment dependant and it would end up copying tons of
>> > paramenters from docker.
>> >
>> > However, having an official docker file and docker image published in
>> the
>> > dockerhub would greatly help others too run servers or build their own
>> > customizations on top of it.
>> >
>> > I'm happy to work on it if that is fine.
>> >
>> >
>> > 2015-09-23 13:28 GMT-07:00 Clebert Suconic <clebert.suco...@gmail.com>:
>> >
>> > > It's just an idea a had for a while... and I couldn't find a way to
>> > > implement it.
>> > >
>> > > It would be nice if we could create an artemis server with a --docker
>> > > option...
>> > >
>> > > ./artemis create --docker ... etc..
>> > >
>> > > From the little I researched, docker offers the image ready, etc... so
>> > I'm
>> > > not sure it makes sense. but if it did it would be a cool feature...
>> > >
>> > >
>> > > Does anyone have any idea on how that could be done? and if that makes
>> > > sense or not?
>> > >
>> >
>>
>>
>>
>> --
>> Clebert Suconic
>>
>
>
