Colin Walters b924c7d843 syscontainers: Don't start on install ...

Interactive users or deployment systems may want to perform
configuration before starting.  For example, I may want to configure
the flannel data in etcd before starting flannel.

This topic comes up a lot in the RPM/deb worlds too; most RPM
distributions are inconsistent about this, whereas Debian basically
never starts a service on package install.

I think also it's better to teach admins to use systemd for service
management directly.

(This commit also changes things so we only `enable` on initial install,
 which is a minor tweak)

Closes: #584
Approved by: rhatdan

2016-09-06 20:25:51 +00:00

..

integration

syscontainers: Don't start on install

2016-09-06 20:25:51 +00:00

test-images

syscontainers: track installed files with systemd-tmpfiles

2016-08-30 11:28:22 +00:00

unit

Split out atomic pull functions into their own source file.

2016-09-01 19:02:07 +00:00

atomic-client.js

Handle cases where container does not have a Status key

2016-08-04 14:28:08 +00:00

atomicClient.html

DBus API to retrieve images data and vulnerability information

2016-07-29 19:08:27 +00:00

integration_template.sh

Integrate remote inspection with Atomic info.

2015-07-20 16:16:12 -04:00

manifest.json

DBus API to retrieve images data and vulnerability information

2016-07-29 19:08:27 +00:00

unit_template.py

New test framework.

2015-07-10 14:09:37 -04:00