lxc
Here are 207 public repositories matching this topic...
It would be nice to have snapshots.schedule support the @reboot keyword. Such schedule would mean a snapshot would be taken just before starting the instance.
It would also be nice for the snapshots.expiry to support a syntax like 3@reboot to keep the past 3 snapshots taken before startups. This would likely require the snapshots name to have a snapshots.pattern including the reboot
-
Updated
Apr 9, 2020 - Go
LXD support ?
Hi !
Are you planning to support LXD soon ?
Supporting LXD would be absolutely awesome, no more local daemon + beneftis of lxd raw protocol ...
Thanks for this project !
Cloning a container from /ui/containers copies the mac address for the container.
web6 was created by using lxc copy web5 web6 but web5 was created by using the clone option in the UI.
It seems like LXC knows to change mac addresses when starting the new container but the UI j
When using the sample lxdock.yml, I get containers whose names are <project name>-<container name>-<some digits>.
+--------------------------+---------+---------------------+------+------------+-----------+
| myproject-test01-5902851 | RUNNING | | | PERSISTENT | 0 |
+
Many of version checking related functions (e.g.
lxc.VersionNumber, lxc.VersionAtLeast, VERSION_AT_LEAST ` refer to the lxc versions present at compile time in build host rather
Setting Memory Limit
After i set memory limit in LXC-Web_Panel, i get this error.
lxc-start 1458216455.373 ERROR lxc_cgmanager - cgmanager.c:cgm_setup_limits:1378 - call to cgmanager_set_value_sync failed: invalid request
lxc-start 1458216455.373 ERROR lxc_cgmanager - cgmanager.c:cgm_setup_limits:1381 - Error setting cgroup memory:lxc/redis limit type memory.memsw.limit_in_bytes
lxc-start 14582
tests != docs.
It becomes very complicated start to use and contribute to this project, because it lacks documentation, apparently referring to unit testing, as if it were an appropriate way to start, but they are not.
Maybe for beginners like me it is complicated, but the idea is that everyone can contribute, or at least try.
Hello,
It would be nice if we could create Windows images for LXD automatically.
Obviously we won't be able to publish such images so we'll have to instruct users
to build them themselves.
For the installation we can extract the wim/esd image using wimapply(from wimlib) + an unattended.xml
And for the customization of the OS we can use cloudbase-init as mentioned here lxc/lxd#6205
This s
Im not particularly well versed in all of LXD networking features (or networking in general), so please advise on what you want to see,
The features should apply to a wide a user base as possible , also be aware of the data that is returned by the LXD Rest API it may not be possible to calculate or perform some of the complex
LXD Network Health
-
Updated
Mar 1, 2019 - C++
I created 10 containers, then, destroyed them all (muahaha).
Looking at lxc-ls and ifconfig I can see that the containers are still "running" but trying to execute lxc-destroy --name *** gives back an error
f87efd19-4594-407d-9b18-712273144675 RUNNING 10.0.3.130 - - NO
root@Sphere:/var/lib/lxc# lxc-destroy --name f87efd19-4594-407d-9b18-712273144675
Container is not d
-
Updated
Sep 8, 2017 - Shell
-
Updated
Feb 2, 2018 - Python
Livio
for LXDhub
When I had my LXD remote repository up and running on an instance in the Hetzner Cloud I had 23 application "images" there.
They were:
- bpm
- civicrm
- discourse
- dokuwiki
-
Updated
Apr 6, 2019 - Vue
-
Updated
May 8, 2020 - C#
We want to add support for AzureStack, Microsoft's hybrid cloud. However the documentation in the Wiki on doing this is not clear. Also, all the comments are TBD for each cloud operation.
-
Updated
Mar 8, 2020 - Shell
-
Updated
May 19, 2020 - Shell
-
Updated
Feb 14, 2018 - C
Image download links are in the setup guide. Feel free to create a pull request if the links are broken
Improve this page
Add a description, image, and links to the lxc topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the lxc topic, visit your repo's landing page and select "manage topics."

After the addition of NFTables in 3.22 (Issue: lxc/lxd#6223 / PR: lxc/lxd#6875), the lxc-checkconfig script should be updated to reflect the new optional kernel configuration requirements (more or less optional, if more Linux distributions drop iptables support).
(... and a