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}

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='https://ngx.rktmb.org/foo' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='https://ngx.rktmb.org/foo&

dockerfile multiline to file

Outputing a multiline string from Dockerfile I motsly use a Dockerfile by sourcing from a base ditribution: CentOS or Debian. But I also have a local mirror and would like to use it for packages installation. Espacially on CentOS it is about many lines to write to the /etc/yum.repos.d/CentOS-Base.repo file. Easiest way: one RUN per line The first method that comes in mind is to issue one RUN per line to write. Here you are: RUN echo "[base] " > /etc/yum.repos.d/CentOS-Base.repo RUN echo "name=CentOS-$releasever - Base " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "baseurl=ftp://packages-infra.mg.rktmb.org/pub/centos/7/base-reposync-7 " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "gpgcheck=0 &quo

Emacs TypeScript Development

Emacs Configuration for Typescript In order to comfortably develop on Node, React or Angular projects with Emacs, TIDE is a good solution. We have TypeScript code highlight (that is the minimum!) and code completion based on the codebase (not only on locally defined and builtins) In order to achieve that: Install Emacs (24+) Install Node Install Typescript (which will provide "tsserver") Install TIDE and some usefull dependencies Configure Emacs to use all those Node is then installed in " /home/mihamina/Apps/node-v12.18.0-linux-x64/bin ": you should add it to your PATH. Installing Typescript is done with: npm install --save typescript @types/browserify After that, "tsserver" will be in " /home/mihamina/node_modules/.bin " Then comes the installation of TIDE: With the Emacs package manager, M-x package-install , install "tide". Do the same for "web-mode", "flycheck", "company" "js2-mode" and "