| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
meta-agl-lxc is no longer reflecting the actual content and use of the layer.
Rename it to 'meta-agl-ic-container' and the feature to 'agl-ic-container'.
Also rename the main image to 'agl-cluster-demo-lxc-host' to match the pattern used
by all other images e.g. agl-<ivi,cluster,telematics>-demo-* .
But keep the names of the underlying images as-is.
Bug-AGL: SPEC-4464
Signed-off-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
Change-Id: I898c786ca884331b302a3be8e150379fcf5bdc9b
|
|
-add wireplumber-policy-config-agl recipe to guest, while
wireplumber-config-agl remains in host.
-add packagegroup-pipewire-base which is needed by the policy recipe.
-mount host pipewire server socket in /var directory in guest image and
define a PIPEWIRE_RUNTIME_DIR environment variable based on this new mount
point.
-make the needed service file changes to have wireplumber policy
instance start on its own with out depending on pipewire service, limit this
change to lxc layers.
-install wireplumber@policy.service in sockets.targets.want directory,
this is need for its self start, limit this change to lxc layers
Bug-AGL: SPEC-4100
Signed-off-by: Ashok Sidipotu <ashok.sidipotu@collabora.com>
Change-Id: Ifbd7a026c75a199bb540c1593d5a93f67a4bde02
|
|
Existing lxc config creation recipe is supporting two type string
replacing. The network interface setting has required to multi line
replacing at aec683913cd645fcf18d7633a12a7b4b42215f69.
These flexibility will support by container manager that is under
developing. But we need quick solution for that now.
This patch provide quick solution. This patch support any network
interface usage in guest.
Bug-AGL: SPEC-4132
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: I5da97492610124ddfe050660e0cc2c2c5559d5b9
|
Jan-Simon Moeller
Ashok Sidipotu
Naoto Yamaguchi