Skip to main content

archlinux lxc debian centos container

Create Debian8 and CentOS7 LXC containers on Archlinux host

Using LXC to create Debian 8 and CentOS 7 containers require to play with AUR.

In order to ease the work:

# pacman -S base-devel

In  /etc/pacman.conf
[archlinuxfr]
SigLevel = Never
Server = http://repo.archlinux.fr/$arch

# pacman -S lxc arch-install-scripts netctl
# pacman -S yaourt
$ yaourt -S debootstrap yum

This last command will pull several packages from AUR then expect some long time compiling
I dont really know why, but I had to reboot to have everything working smoothly.

Create a CentOS7 container


# export CONTAINER_NAME=c7-00
# lxc-create  -t centos --name ${CONTAINER_NAME} -- --release 7 --arch x86_64 \
               --repo YOU_CUSTOM_REPO

Then edit the configuration:
# nano -w /var/lib/lxc/${CONTAINER_NAME}/config

Mine looks like this

lxc.rootfs = /var/lib/lxc/c7-00/rootfs
lxc.include = /usr/share/lxc/config/centos.common.conf
lxc.arch = x86_64
lxc.utsname = c7-00
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br0
lxc.network.name = eth0
lxc.network.ipv4 = 192.168.128.130/23
lxc.network.ipv4.gateway = 192.168.128.1
lxc.network.hwaddr = 9e:32:da:11:44:5e

Start the container with the previous settings:
# lxc-start --name ${CONTAINER_NAME}

Enter the container
# lxc-attach --name ${CONTAINER_NAME}

# export PATH="/sbin:"${PATH}
# yum install -y nano

Install a Debian8 container

# export CONTAINER_NAME=b7-00
# lxc-create  -t debian --name ${CONTAINER_NAME} -- --mirror=YOUR_MIRRORdebian/ \
      --release=jessie --security-mirror=YOUR_MIRROR/debian-security/ --arch=x86_64

Then edit the configuration:
# nano -w /var/lib/lxc/${CONTAINER_NAME}/config

Mine looks like this

lxc.rootfs = /var/lib/lxc/d8-00/rootfs
lxc.include = /usr/share/lxc/config/debian.common.conf
lxc.utsname = d8-00
lxc.arch = amd64
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br0
lxc.network.name = eth0
lxc.network.ipv4 = 192.168.128.128/23
lxc.network.ipv4.gateway = 192.168.128.1
lxc.network.hwaddr = 9e:32:da:11:44:5a

Start the container with the previous settings:
# lxc-start --name ${CONTAINER_NAME}

Enter the container
# lxc-attach --name ${CONTAINER_NAME}

# export PATH="/usr/sbin:/sbin:/bin:"${PATH}

Comments

Popular posts from this blog

vmware libz libfontconfig libexpat

Archlinux - Kernel 4.11 - VMWare workstation 12.5.7 With this combination, when I launch "vmware", despite the fact I already "export VMWARE_USE_SHIPPED_LIBS=force", I get those lines:

Unable to load libfontconfig.so.1. /usr/lib/vmware/lib/libz.so.1/libz.so.1: version `ZLIB_1.2.9' not found (required by /usr/lib/libpng16.so.16) Unable to load libfontconfig.so.1 from /usr/lib/vmware/lib/libfontconfig.so.1/libfontconfig.so.1: libexpat.so.0: cannot open shared object file: No such file or directory Unable to load dependencies for /usr/lib/vmware/lib/libvmware-modconfig.so/libvmware-modconfig.so
In order to workaround, I decided to get the things to the maximum: Add all shipped libraries in the LD_LIBRARY_PATH.

So I created my custom launcher of "vmware" and this is the content:

#!/bin/bash
export VMWARE_USE_SHIPPED_LIBS=force
LD_LIBRARY_PATH=""
LD_LIBRARY_PATH=$( find /usr/lib/vmware/lib/ -maxdepth 1 -mindepth 1 -type d | awk 'BEGIN{p=&quo…

vmware net_device trans_start

VMWare Workstation 12 and Kernel 4.7 When recompiling vmware kernel modules on a kernel 4.7, I get this error:

/tmp/modconfig-xrrZGZ/vmnet-only/netif.c:468:7: error: ‘struct net_device’ has no member named ‘trans_start’; did you mean ‘mem_start’?     dev->trans_start = jiffies;
This seems to be an already encountered problem: http://rglinuxtech.com/?p=1746http://ferenc.homelinux.com/?p=356 I choosed to replace the line, instead of deleting it.

- dev->trans_start = jiffies; + netif_trans_update(dev); I also noted that I had to re-tar the modified sources instead of leaving them untared, because the compilation process only takes the archives. 
On precedent editions of these files, I just left the modified folders "vmnet-only/" and "vmmon-only/" expanded without the need to re-tar them.


Jira workflow for new projects

Associated workflow creation I'm a Jira Cloud user and begining from some version 6, I noticed that when I create a project, it automatically creates a Workflow and Issue Scheme that is prepended by the project key and which is a copy of the default scheme.
I always had to make a cleanup after creating a project. Default workflow for new projects I also miss a feature that would allow me to make a custom workflow (and globally custom project setting) the default for new projects I create.
Solution: Create with shared configuration While searching, I noticed that with Jira Cloud which is version 7.1.0 at the time I write, there is a link at the bottom of the "Create project" wizard:
"Create with shared configuration" will allow me to select the project I want the new one to share configuration with.

The new created project will use the same configuration as the project I selectThere will be no creation of Workflow and Issue Scheme that I need to cleanup

This fea…