Skip to main content

Make build Env. for Golang and zmq in Chroot


https://github.com/doohee323/buildGoInChroot

When you need to build Golang app. in different ubuntu version, you can use chroot. I made it for the usecase. It makes chroot environment and a builds debian file. And I made a lucid with vagrant, and installed below 3 ubuntu version debians in it. Since ZMQ library is needed for this app, only lucid debian can run in lucid VM.

Required

    1. install chroot
        apt-get install dchroot
        apt-get install debootstrap

    2. edit chroot configuration
        vi /etc/schroot/schroot.conf

        [precise]
        description=Ubuntu precise
        location=~/chroot/precise
        priority=3
        users=hello
        group=hello
        root-groups=root

        [lucid]
        description=Ubuntu lucid
        location=~/chroot/lucid
        priority=3
        users=hello
        group=hello
        root-groups=root

        [trusty]
        description=Ubuntu trusty
        location=~/chroot/trusty
        priority=3
        users=hello
        group=hello
        root-groups=root

How to run

    $ bash chroot.sh lucid 1.0
        - 1st arg: ubuntu version precise / lucid / trusty ...
        - 2nd arg: want to build version
    $ bash chroot.sh precise 1.0
    $ bash chroot.sh trusty 1.0

Verify in lucid

    - install vagrant 4.3
    https://www.virtualbox.org/wiki/Download_Old_Builds_4_3
    - add lucid in vagrant
    vagrant box add lucid64 http://files.vagrantup.com/lucid64.box
    - run vm
    vagrant up
    vagrant@hello:/vagrant$ hello server

    - open another terminal and run hello with client argument.
    vagrant ssh
    vagrant@hello:/vagrant$ hello client
    => it works!

    - but When you install hello_precise.deb in lucid, you'll get this error! 
    dpkg -i hello_precise.deb
    vagrant@hello:/vagrant$ hello server
    => hello: /lib/libc.so.6: version `GLIBC_2.14' not found (required by hello)

Comments

Popular posts from this blog

DevOps JD's required skills from LinkedIn

From some of DevOps JD on linkedIn, I realised that DeveOps should be the leader of the organization. https://docs.google.com/spreadsheets/d/1P520nH0pYcAdN0rJcnMQqsgu9cV9GdknztJ92J8l7-s/pubhtml DevOps' Required Skills From LinkedIn on 8/30/16: DevOps should be the leader of the company! Yahoo Netflix Samsung Salesforce Fortinet SUM OS admin UNIX systems Unix platforms Linux administrator Linux VMs Docker VMs VMware, OpenStack, Hyper-V Openstack, KVM, VMWare Version control version control systems Git, SVN Cloud Amazon AWS AWS AWS, Azure DB MySql Oracle, MySQL, NoSQL Mysql administration and strong command of SQL MySQL RabbitMQ MySql, MongoDB, Redis, Oracle, ProgreSQL N/W TCP/IP networking, DNS, HTTP NAS Understanding of network stack, network tuning, subnet/VLANs. HAProxy, DNS, IPTable Script Lang Shell, Perl, Python, Ruby, PHP bash Python, Bash/tcsh a scripting language: Perl, Python and Unix Shell preferred Python, Perl, Ruby Python, Ruby, Shell, PHP Web LAMP stack

Ubuntu GUI with VNC on Xenserver

Xenserver 에서 Ubuntu GUI 를 쓰기 위해서는 VNC 가 답인 듯... Installing Ubuntu Gnome GUI on Ubuntu Server 12.10 with VNC Update Repositories # apt-get update Install gnome and vnc: # apt-get install gnome-core vnc4server Start VNC Server: # vncserver (You’ll then be prompted to create and verify a new VNC connect password) Kill the currently running VNC Session: # vncserver -kill :1 Edit VNC startup config file: # vim .vnc/xstartup Uncomment the following line: unset SESSION_MANAGER Add the following line: gnome-session --session=gnome-classic & Comment Out the following two lines: x-terminal-emulator -geometry 1280x1024+10+10 -ls -title "$VNCDESKTOP Desktop" & x-window-manager & End result should look like: #!/bin/sh # Uncomment the following two lines for normal desktop: unset SESSION_MANAGER # exec /etc/X11/xinit/xinitrc gnome-session --session=gnome-classic & [ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup [ -r $HOME/

Install CoreOs on linode without VM

Install CoreOs on linode without VM 1. Add a Linode 2. Create a new Disk   CoreOS 3. Rescue > Reboot into Rescue Mode 4. Remote Access   Launch Lish Console 5. make an install script cat <<'EOF1' > install.sh # add needed package sudo apt-get update sudo apt-get install -y curl wget whois sudo apt-get install -y ca-certificates #sudo apt-get install gawk -y # get discovery url discoveryUrl=`curl https://discovery.etcd.io/new` # write cloud-config.yml cat <<EOF2 > cloud-config.yml #cloud-config users:   - name: core     groups:       - sudo       - docker coreos:   etcd:     name: node01     discovery: $discoveryUrl hostname: node01 EOF2 # get the coreos installation script #wget https://raw.github.com/coreos/init/master/bin/coreos-install wget https://raw.githubusercontent.com/coreos/init/master/bin/coreos-install # run installation chmod 755 coreos-install sudo ./coreos-install \       -d /dev/sda \       -