Yes, Nulecule can help you. The docker provider is what you are looking
for.

See
https://github.com/projectatomic/nulecule/tree/master/examples/helloapache/Nulecule
and then go to artifacts/docker and see the file there. Docker provider
does not limit you in what command you want to run. Sadly, we were not get
to parsing labels directly, that's why you have to drop your run command to
a plain text file (but OTOH it let's you to use params in Nulecule file
which would be a bit more complicated with using RUN label).

If you think using lables would be better fit for you, we can take a look
at something like atomic provider (or you can just send a PR:) )

Let us know in case of any quesitons.

Cheers,
VaĊĦek




On Mon, Aug 24, 2015 at 3:49 PM, Matt Micene <[email protected]> wrote:

> If so, is there some
>> "atomic" provider that installs all containers that a nulecule specifies?
>
>
>  Check out Atomicapp https://github.com/projectatomic/atomicapp
>
> Nulecule is the specification for handling multi-container multi-provider
> applications.  Atomicapp is a reference implementation that consists of a
> tool that can deploy Nulecule defined apps.  There is an Atomicapp
> container that can be used as a base layer with atomic that uses docker
> LABELs to provide run instructions.  I've not tried a SPC container with an
> Atomicapp.
>
> cc'ing container-tools list to get some visibility to the
> Nulecule/Atomicapp folks.
>
> - Matt M
>
> On Mon, Aug 24, 2015 at 9:37 AM, Colin Walters <[email protected]> wrote:
>
>> On Fri, Aug 21, 2015, at 09:07 AM, Tobias Florek wrote:
>> > Hi,
>> >
>> > is there a way to specify dependencies for (spc) containers that provide
>> > some service?
>>
>> This is an interesting topic; both raw docker and kubernetes lack
>> dependency mechanisms.  I think down the line, kubernetes is going
>> to have to grow this to some degree.  Currently one can basically just
>> do retry/backoff loops in applications.
>>
>> > Is nulecule the way to do it? If so, is there some
>> > "atomic" provider that installs all containers that a nulecule
>> specifies?
>>
>> We don't have a best practice around this yet that I'm aware of, but I
>> would
>> approach it with systemd units whose ExecStart=docker run.  (Or if you
>> want
>> in the future, drop to runc, or use systemd-nspawn)
>>
>> I think you could indeed use nulecule to handle pulling multiple images
>> and generating unit files to install them.
>>
>>
>
> _______________________________________________
> Container-tools mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/container-tools
>
>


-- 
Architect - Senior Software Engineer
Developer Experience
Brno, Czech Republic
Phone: +420 739 666 824

Reply via email to