Create Snappy Ubuntu as a Docker Image

-
Snappy ubuntu core is the latest member of ubuntu family that specifically designed to run on Linux containers. To put it simple it's a stripped down ubuntu with some advanced features such as transactional upgrades/rollback to bring more stability, security with AppArmor and new snappy package manager instead of apt-get.

I wanted to run snappy ubuntu on a docker container, however I couldn't find the base snappy image on the docker hub to pull. So I decided to make and push it myself to docker hub.

First we need to download the Snappy image. It can be downloaded from https://developer.ubuntu.com/en/snappy/start/#try-x86

# wget http://releases.ubuntu.com/15.04/ubuntu-15.04-snappy-amd64-generic.img.xz

It comes as a XZ compressed IMG filesystem dumped image. we will unzx it:

# unzx ubuntu-15.04-snappy-amd64-generic.img.xz

For ISO images we simply can loop mount and access them:

# mkdir /mnt/iso
# mount -o loop image.iso /mnt/iso

And proceed to read the mounted directory as tar and create the docker image from STDIN:

 # tar -C /mnt/iso -c . | docker import - yourrepo/yourimage:anytag


However, for IMG dump images it's a bit hassle-y:

1. Load the nbd kernel module with max_parts option if you are in a debian-based machine:

# modprobe nbd max_parts=16

 2. Mount the image to /dev/nbd0 with qemu:

 # qemu-nbd -c /dev/nbd0 ubuntu-15.04-snappy-amd64-generic.img

 3. Ask kernel to re-read the partition table:

 # partprobe /dev/nbd0


We can see the filsystem within this image via fdisk:

# fdisk -l /dev/nbd0

 Disk /dev/nbd0: 3,6 GiB, 3899999744 bytes, 7617187 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 374F5ED9-98FE-47B5-B430-A8983D7CB41B

 Device Start End Sectors Size Type

 /dev/nbd0p1 8192 16383 8192 4M BIOS boot
/dev/nbd0p2 16384 278527 262144 128M EFI System
/dev/nbd0p3 278528 2375679 2097152 1G Linux filesystem
/dev/nbd0p4 2375680 4472831 2097152 1G Linux filesystem
/dev/nbd0p5 4472832 7614463 3141632 1,5G Linux filesystem


Our desired contents are located in nbd0p3, so we will mount it:

# mount /dev/nbd0p3 /mnt/snappy/

There we are! We have all that is required to create our docker image:

# tar -C /mnt/snappy/ -c . | docker import - arvinep/ubuntu:snappy

To check the newly created image, let's list the local docker images:

# docker images
REPOSITORY            TAG    IMAGE ID      CREATED        VIRTUAL SIZE
arvinep/ubuntu-snappy snappy 2e796faa9adc  9 minutes ago  604.8 MB
ubuntu                latest d55e68e6cc9c  26 hours ago   187.9 MB

Cool! Let's run it and access to our docker container:

# docker run -it arvinep/ubuntu:snappy /bin/bash

It's up and running alongside with other docker containers:

# docker ps
CONTAINER ID   IMAGE                 COMMAND      CREATED             STATUS              PORTS  NAMES
25d60fa0238d   arvinep/ubuntu:snappy "/bin/bash"  About a minute ago  Up About a minute          sleepy_banach       
1cff710b5604   ubuntu:latest         "/bin/bash"  2 hours ago         Up 2 hours                 angry_davinci       
afe31fbcbf7d   ubuntu:latest         "/bin/bash"  2 hours ago         Up 2 hours                 serene_lovelace     
74a46b4b203f   ubuntu:latest         "/bin/bash"  2 hours ago         Up 2 hours                 tender_bartik    


I have pushed the snappy ubuntu to docker hub so you can pull and enjoy it:

# docker run -it arvinep/ubuntu-snappy /bin/bash


Comments

  1. Essay Writing11 April 2020 at 22:20

    It does not appear too complicated when it comes to creating a new snappy Ubuntu as a docker image. It seems to be quite clear.

    ReplyDelete

Post a Comment

Popular posts from this blog

Linux and AIX user non expiry and force password change at first login

-
In Linux, if you want to set the password for an account to never expire, here is the command: # chage -I -1 -m 0 -M 99999 -E -1 username  And to force a user to change his password upon first login: # chage -d0 username Current status of the account can be checked via chage command : # chage -l username  Last password change                                    : Jun 18, 2013 Password expires                                        : never Password inactive                                       : never Account expires                                         : never Minimum number of days between password change          : 0 Maximum number of days between password change          : 99999 Number of days of warning before password expires       : 7 For AIX, to set the password to non expiry and force the user to change his password upon first login: # chuser expires=0 maxage=0 username  To check the username status in AIX: # lsuser -f username
Read more

Rebuild your new Yum repository after changing the packages

-
If you have done any  changes  to your local  repository  packages, adding new ones or deleting some, you can just simply update your yum sqlite metadata database for your changes to take effect, rather than creating the whole repository again which takes time if you have  thousands  of packages in your repository.  Here is how we rebuild our yum repository. 1. After you are done with adding/removing packages to your local repo, then: # createrepo --update /path/to/repo_dir 2. On the  client  side, you need to clean up the cached yum meta data in order to see the changes after repo rebuild: # yum clean all 3. Now update the  client  yum cache  # yum update
Read more

Running Docker Wildfly/JBoss Application Server in Debug mode via Eclipse

-
I have recently built the whole Development Environment of Java Enterprise Edition (J2EE) project on multiple Docker containers. It has saved the hassle of setting up a dev env for new developers. All it takes to setup the environment is to clone our github repositories and run the Docker images. I will explain the setup in a future post. Build Wildfly Docker Image with Debugging Enabled So basically in order to run the Wildfly in debug mode, we need to add --debug  flag to the Wildfly standalone.sh  startup script. Also we need to expose port 8787  in our image as it's the default port for Wildfly JVM debug mode. 1. Create or change your Wildfly Dockerfile as follows: $ cat Dockerfile FROM jboss/wildfly: 10.0 . 0 .Final EXPOSE 8787 CMD [ "/opt/jboss/wildfly/bin/standalone.sh" , "-b" , "0.0.0.0" , "-bmanagement" , "0.0.0.0" , "--debug" ] 2. Build and tag the image: $ docker build -t wildfly-debug . 3.
Read more