Enable Microstack install in LXD container

Bug #1883435 reported by Allan Roman Reyes
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MicroStack
Triaged
Wishlist
Unassigned

Bug Description

Previous bug subject: Microstack install error on Ubuntu(bionic) LXD linuxcontainers.org image

local mc uname:Linux ubuntu-kit 5.4.0-1012-raspi #12-Ubuntu SMP Wed May 27 04:08:35 UTC 2020 armv8l armv8l armv8l GNU/Linux

journalctl of Microstack --classic --beta snap install: Jun 14 15:40:50 ubuntu-kit systemd[1]: networkd-dispatcher.service: Failed to reset devices.list: Operation not permitted
Jun 14 15:40:50 ubuntu-kit systemd[1]: system-getty.slice: Failed to reset devices.list: Operation not permitted
Jun 14 15:40:50 ubuntu-kit systemd[1]: systemd-resolved.service: Failed to reset devices.list: Operation not permitted
Jun 14 15:40:50 ubuntu-kit systemd[1]: Failed to set devices.allow on /system.slice/systemd-resolved.service: Operation not permit
Jun 14 15:40:50 ubuntu-kit systemd[1]: Failed to set devices.allow on /system.slice/systemd-resolved.service: Operation not permit
Jun 14 15:40:50 ubuntu-kit systemd[1]: Failed to set devices.allow on /system.slice/systemd-resolved.service: Operation not permit
Jun 14 15:40:50 ubuntu-kit systemd[1]: Failed to set devices.allow on /system.slice/systemd-resolved.service: Operation not permit
Jun 14 15:40:50 ubuntu-kit systemd[1]: Failed to set devices.allow on /system.slice/systemd-resolved.service: Operation not permit
Jun 14 15:40:50 ubuntu-kit systemd[1]: Failed to set devices.allow on /system.slice/systemd-resolved.service: Operation not permit
Jun 14 15:40:50 ubuntu-kit systemd[1]: Failed to set devices.allow on /system.slice/systemd-resolved.service: Operation not permit
Jun 14 15:40:50 ubuntu-kit systemd[1]: Failed to set devices.allow on /system.slice/systemd-resolved.service: Operation not permit
Jun 14 15:40:50 ubuntu-kit systemd[1]: snap.mount: Failed to reset devices.list: Operation not permitted
Jun 14 15:40:50 ubuntu-kit systemd[1]: keyboard-setup.service: Failed to reset devices.list: Operation not permitted
Jun 14 15:40:50 ubuntu-kit systemd[1]: rsyslog.service: Failed to reset devices.list: Operation not permitted
Jun 14 15:40:50 ubuntu-kit systemd[1]: snapd.service: Failed to reset devices.list: Operation not permitted
Jun 14 15:40:50 ubuntu-kit systemd[1]: systemd-udevd.service: Failed to reset devices.list: Operation not permitted
Jun 14 15:40:50 ubuntu-kit systemd[1]: sys-fs-fuse-connections.mount: Failed to reset devices.list: Operation not permitted
Jun 14 15:40:50 ubuntu-kit systemd[1]: console-getty.service: Failed to reset devices.list: Operation not permitted
Jun 14 15:40:50 ubuntu-kit systemd[1]: systemd-modules-load.service: Failed to reset devices.list: Operation not permitted
Jun 14 15:40:50 ubuntu-kit systemd[1]: snap-core-9291.mount: Failed to reset devices.list: Operation not permitted
Jun 14 15:40:50 ubuntu-kit systemd[1]: sys-kernel-config.mount: Failed to reset devices.list: Operation not permitted
Jun 14 15:40:54 ubuntu-kit snapd[1189]: handlers.go:495: Reported install problem for "microstack" as 6d021556-ae55-11ea-a618-fa16
Jun 14 15:40:54 ubuntu-kit sudo[1038]: pam_unix(sudo:session): session closed for user root

Revision history for this message
Corey Bryant (corey.bryant) wrote :

Hi Allan,

Thanks for reporting this. We currently don't test MicroStack in containers and it's getting into uncharted territory. For now, this doesn't fit with the project goals, however that's not to say that we won't support running in containers in the future. We're just focused on getting MicroStack featureful and solid on metal at this point.

Thanks,
Corey

summary: - Microstack install error on Ubuntu(bionic) LXD linuxcontainers.org image
+ Enable Microstack install in LXD container
description: updated
Changed in microstack:
status: New → Triaged
importance: Undecided → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.