Archives/gitian-builder
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
f4b72bbec4
gitian-builder/etc/lxc.config.in

36 lines
1.1 KiB
Plaintext
Raw Normal View History

First pass lxc support
2012-04-22 05:44:00 +00:00
lxc.tty = 4
lxc.pts = 1024
lxc.rootfs = ROOTFS
lxc.arch = ARCH
lxc.cgroup.devices.deny = a
# /dev/null and zero
lxc.cgroup.devices.allow = c 1:3 rwm
lxc.cgroup.devices.allow = c 1:5 rwm
# consoles
lxc.cgroup.devices.allow = c 5:1 rwm
lxc.cgroup.devices.allow = c 5:0 rwm
lxc.cgroup.devices.allow = c 4:0 rwm
lxc.cgroup.devices.allow = c 4:1 rwm
# /dev/{,u}random
lxc.cgroup.devices.allow = c 1:9 rwm
lxc.cgroup.devices.allow = c 1:8 rwm
lxc.cgroup.devices.allow = c 136:* rwm
lxc.cgroup.devices.allow = c 5:2 rwm
# rtc
lxc.cgroup.devices.allow = c 254:0 rwm
# mounts points
lxc.mount.entry=proc ROOTFS/proc proc nodev,noexec,nosuid 0 0
lxc.mount.entry=sysfs ROOTFS/sys sysfs defaults 0 0
# Container with network virtualized using a pre-configured bridge named br0 and
# veth pair virtual network devices
# On the host, run: ifconfig br0 up 10.0.2.2
Un-hardcode host/guest IP I was running into trouble using gitian LXC INSIDE a VirtualBox VM, because the 10.0.2.x IP range overlaps with the range that VirtualBox uses for its internal NAT network. This commit makes it possible to override the host and guest IP that is used during LXC image creation and the build, using environment variables: - `GITIAN_HOST_IP` (default=10.0.2.2, host IP from the viewpoint of the VM, can be used for both LXC and KVM) - `LXC_GUEST_IP` (default=10.0.2.5, guest IP from the viewpoint of the host, effective for LXC only) When these are not defined the behavior remains the same as before.
2014-04-02 12:56:29 +00:00
# Alternatively, you can use another IP range for the bridge interface, in this case set
# the environment variables GITIAN_HOST_IP and LXC_GUEST_IP appropriately.
First pass lxc support
2012-04-22 05:44:00 +00:00
lxc.network.type = veth
lxc.network.flags = up
Make it possible to override bridge if for LXC For example Ubuntu installs a bridge called `virbr0` by default for LXC. Using this system-provided bridge avoids having to configure one specifically before gitian building. This commits makes it possible to override the bridge used by gitian using the environment variable LXC_BRIDGE. The default is still to use `br0` as before.
2014-04-04 07:55:02 +00:00
lxc.network.link = GUESTLINK
Un-hardcode host/guest IP I was running into trouble using gitian LXC INSIDE a VirtualBox VM, because the 10.0.2.x IP range overlaps with the range that VirtualBox uses for its internal NAT network. This commit makes it possible to override the host and guest IP that is used during LXC image creation and the build, using environment variables: - `GITIAN_HOST_IP` (default=10.0.2.2, host IP from the viewpoint of the VM, can be used for both LXC and KVM) - `LXC_GUEST_IP` (default=10.0.2.5, guest IP from the viewpoint of the host, effective for LXC only) When these are not defined the behavior remains the same as before.
2014-04-02 12:56:29 +00:00
lxc.network.ipv4 = GUESTIP/24
improved LXC support fixes #86
2015-05-17 03:48:18 +00:00
lxc.utsname = gitian
Reference in New Issue Copy Permalink