Chameleon Powered Containers In Amazon EC2 | SUSE Communities

Chameleon Powered Containers In Amazon EC2


Way back when SUSE Linux Enterprise Server 12 was released, just about a year ago, Docker was included as a technology preview. Then earlier this year the Containers Module for SLES 12 was released and Docker became fully supported in SUSE Linux Enterprise. This past week we took the next step in the Docker integration story with the release of updated SUSE Linux Enterprise Server 12 on demand images in Amazon EC2 that have the Containers Module repositories, as well as the new Toolchain Module repositories registered by default. These images are available in all regions and also have Docker installed by default. The images were released on October 2nd, can be found in the general catalog by searching for suse-sles-12-v20151002, and will be linked in the “Quick Launcher” shortly. The docker daemon is not running by default in these images. However, dockerd is enabled in the ECS integrated images that were also released on October 2nd. The ECS images provide full integration with the Amazon EC2 Container Service. Thus, if you are looking for a slimmer version of SLES that just functions as a container host, the SUSE Linux Enterprise Server 12 ECS images may just be the ticket for you. The ECS images can be found in the general catalog by searching for suse-sles-12-v20151002-ecs and are set up as on demand images. This means repositories are automatically registered and you can easily map the /etc/zypp directory into your SUSE Linux Enterprise 12 containers to get access to updates, as well as install additional packages into your container host instance.

If you want to add the containers module to a running instance (SLES 12 only) use the following zypper commands as root.

zypper ar container_module

zypper ar container_module_updates

These are not necessary if you launch instances from the latest SLES 12 images and should not be used for BYOS images. For instances launched from BYOS images replace in the command above with the target that one of your other configured repositories is pointing to, the rest of the URI remains the same.

Once the Containers Module repository is set up you will have access to a later version of Docker than was available in the SLES 12 repository as a technology preview. The containers module also contains the amazon-ecs-int package that provides the integration with ECS. Therefore, you can easily create your own image that is integrated with ECS either in SUSE Studio or with KIWI.

With docker installed in the Amazon EC2 images by default the other frameworks will not be far behind. Watch this blog space for an announcement.

(Visited 1 times, 1 visits today)


  • rjschwei says:

    And as sometimes happens, despite testing and testing and looking at the configuration and code many times over something silly slips through the cracks. In this case it turns out that dockerd and amazon-ecs are actually not running by default as they are supposed to be. The reason being that last minute naming change to the amazon-ecs service did not make it into the image build configuration and we attempt to enable the service using the old name.

    Thus, after firing up the ECS instance ssh into the instance and run.

    systemctl enable docker.service
    systemctl enable amazon-ecs.service

    you can reboot the system at this point and dockerd and amazon-ecs will start upon reboot or instead of rebooting run.

    systemctl start docker.service
    systemctl start amazon-ecs.service

  • Leave a Reply

    Your email address will not be published.