# Docker & SUSE Manager

**URL:** https://forums.suse.com/t/docker-suse-manager/29863
**Category:** SUSE Multi Linux Manager
**Created:** [June 1, 2017, 2:45pm UTC](https://forums.suse.com/t/docker-suse-manager/29863 "2017-06-01T14:45:44Z")
**Posts on this page:** 12
**Page:** 1

<div class="post-metadata">

### Author: ![ollenburg](https://avatars.discourse-cdn.com/v4/letter/o/ce73a5/32.png) [@ollenburg](https://forums.suse.com/u/ollenburg)
#### Post date: [June 1, 2017, 2:45pm UTC](https://forums.suse.com/t/docker-suse-manager/29863/1 "2017-06-01T14:45:44Z")

</div>

Hi,  
we are implementing Docker in our environment and I want to start bulding my own images/containers. The problem: how to install/update software inside my images? We are using SUSE Manager and the Docker hosts are registered against it, do not have acces neither to SCC nor a SMT. Any ideas?  
Greetings  
Andreas

---

<div class="post-metadata">

### Author: ![ab1](https://avatars.discourse-cdn.com/v4/letter/a/d2c977/32.png) [@ab1](https://forums.suse.com/u/ab1)
#### Post date: [June 1, 2017, 4:40pm UTC](https://forums.suse.com/t/docker-suse-manager/29863/2 "2017-06-01T16:40:25Z")

</div>

While I can see that this kind of spans two issues, I think in this case  
the issue is probably more appropriate in the Virtualization area than the  
SUSE Manager area, as I do not think SUSE Manager will be directly  
involved in managing your images. As a result, your duplicate thread is  
probably the best place for this:

[http://forums.suse.com/showthread.php?t=9502](http://forums.suse.com/showthread.php?t=9502)

–  
Good luck.

If you find this post helpful and are logged into the web interface,  
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the  
forum as I do not use the web interface often.

---

<div class="post-metadata">

### Author: ![kwk](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/kwk/32/11997_2.png) [@kwk](https://forums.suse.com/u/kwk)
#### Post date: [June 2, 2017, 9:22am UTC](https://forums.suse.com/t/docker-suse-manager/29863/3 "2017-06-02T09:22:49Z")

</div>

Move to SUSE Manager 3.1, to be released end of June, which has container management included.

---

<div class="post-metadata">

### Author: ![ollenburg](https://avatars.discourse-cdn.com/v4/letter/o/ce73a5/32.png) [@ollenburg](https://forums.suse.com/u/ollenburg)
#### Post date: [June 2, 2017, 9:28am UTC](https://forums.suse.com/t/docker-suse-manager/29863/4 "2017-06-02T09:28:18Z")

</div>

Hi,

I read about the cool new features of SuMa3.1 and was searching for any release dates. Thanks for the info. Four weeks to go… 🙂

Greetings from Germany  
Andreas

---

<div class="post-metadata">

### Author: ![pfoerfr](https://avatars.discourse-cdn.com/v4/letter/p/c37758/32.png) [@pfoerfr](https://forums.suse.com/u/pfoerfr)
#### Post date: [August 17, 2017, 4:14pm UTC](https://forums.suse.com/t/docker-suse-manager/29863/5 "2017-08-17T16:14:48Z")

</div>

Now we have August and SUMA 3.1 is out since end of June!

any news and howto’s available to setup and use SUMA 3.1 as configuration plattforme for docker images?

regards  
Franz

---

<div class="post-metadata">

### Author: ![smflood](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/smflood/32/10576_2.png) [@smflood](https://forums.suse.com/u/smflood)
#### Post date: [August 17, 2017, 6:37pm UTC](https://forums.suse.com/t/docker-suse-manager/29863/6 "2017-08-17T18:37:02Z")

</div>

On 17/08/17 14:24, pfoerfr wrote:  
[color=blue]

> Now we have August and SUMA 3.1 is out since end of June!
> 
> any news and howto’s available to setup and use SUMA 3.1 as  
> configuration plattforme for docker images?[/color]

Have you seen  
[https://www.suse.com/communities/blog/no-beta-blockers-suse-manager-3-1-lets-get-ready-containers/](https://www.suse.com/communities/blog/no-beta-blockers-suse-manager-3-1-lets-get-ready-containers/)  
?

## HTH.

Simon  
SUSE Knowledge Partner

* * *

## If you find this post helpful and are logged into the web interface, please show your appreciation and click on the star below. Thanks.

---

<div class="post-metadata">

### Author: ![pfoerfr](https://avatars.discourse-cdn.com/v4/letter/p/c37758/32.png) [@pfoerfr](https://forums.suse.com/u/pfoerfr)
#### Post date: [August 18, 2017, 11:26am UTC](https://forums.suse.com/t/docker-suse-manager/29863/7 "2017-08-18T11:26:36Z")

</div>

[QUOTE=smflood;39149]On 17/08/17 14:24, pfoerfr wrote:  
[color=blue]

> Now we have August and SUMA 3.1 is out since end of June!
> 
> any news and howto’s available to setup and use SUMA 3.1 as  
> configuration plattforme for docker images?[/color]

Have you seen  
[https://www.suse.com/communities/blog/no-beta-blockers-suse-manager-3-1-lets-get-ready-containers/](https://www.suse.com/communities/blog/no-beta-blockers-suse-manager-3-1-lets-get-ready-containers/)  
?

## HTH.

Simon  
SUSE Knowledge Partner

* * *

If you find this post helpful and are logged into the web interface,  
please show your appreciation and click on the star below. Thanks.  
------------------------------------------------------------------------[/QUOTE]

yes, I know this blog.

but in the usage of this feature some steps are not discribed.

First I have to say I am a docker beginner. And the SUSE docker examples at [https://www.suse.com/documentation/sles-12/singlehtml/book\_sles\_docker/book\_sles\_docker.html](https://www.suse.com/documentation/sles-12/singlehtml/book_sles_docker/book_sles_docker.html) are not working behind our company firewall.

So, my hope was SUMA 3.1 is the solution.

In the meantime I build up a docker-registry with ssl and ldap enabled portus. This seams to be working.

on suse manager, one host is enabled as container-build-host. the salt story did not work … first add the container channels, after this maybe the stuff is working.

I try to follow the blog but the image profiles details not shown.

there are some parameters

Label: - I understood  
Image Type: Dockerfile - only Dockerfile available, choice  
Path: - is real a git necessary? with authentication and so on? why not a http/https url for testing …  
Activation Key: - for the repos … is a separate key necessary with special channels? salt states …  
Custom Info Values: - how could I use them at the container? some special salt states inside of the container

this raises more questions than answers.

regards  
Franz

---

<div class="post-metadata">

### Author: ![kwk](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/kwk/32/11997_2.png) [@kwk](https://forums.suse.com/u/kwk)
#### Post date: [September 1, 2017, 11:00am UTC](https://forums.suse.com/t/docker-suse-manager/29863/8 "2017-09-01T11:00:58Z")

</div>

> [@pfoerfr;39157](#):
>
> First I have to say I am a docker beginner. And the SUSE docker examples at [https://www.suse.com/documentation/sles-12/singlehtml/book\_sles\_docker/book\_sles\_docker.html](https://www.suse.com/documentation/sles-12/singlehtml/book_sles_docker/book_sles_docker.html) are not working behind our company firewall.
> 
> So, my hope was SUMA 3.1 is the solution.

[https://wiki.microfocus.com/index.php/SUSE\_Manager/imagebuilding](https://wiki.microfocus.com/index.php/SUSE_Manager/imagebuilding) has an initial description of the container image building feature of SUSE Manager 3.1.  
A more elaborate chapter in the best practices manual will follow.

> [@pfoerfr;39157](#):
>
> Image Type: Dockerfile - only Dockerfile available, choice

Well, building a container with Docker and a Dockerfile was the obvious initial choice for us.  
There are other means (like Salt - dockerng) and we’ll see what gains sufficient popularity to be supported in SUSE Manager.

> [@pfoerfr;39157](#):
>
> Path: - is real a git necessary? with authentication and so on? why not a http/https url for testing …

Yes, based on the feedback from customers, sales, and consulting, managing Dockerfiles with git is the most popular choice.

Setting up a git server is simple, Google provides many examples

> [@pfoerfr;39157](#):
>
> Activation Key: - for the repos … is a separate key necessary with special channels? salt states …

The activation key determines the channels visible to the client. Building containers is all about having the ‘right’ packages in the container. This is ensured via the activation key.

> [@pfoerfr;39157](#):
>
> Custom Info Values: - how could I use them at the container? some special salt states inside of the container

Leave this field empty for your initial tests.

---

<div class="post-metadata">

### Author: ![so\_it\_team](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@so\_it\_team](https://forums.suse.com/u/so_it_team)
#### Post date: [November 14, 2017, 3:16pm UTC](https://forums.suse.com/t/docker-suse-manager/29863/9 "2017-11-14T15:16:15Z")

</div>

I am also struggling with this, for example;

1. For the Image Store URI, I intend to use a Portus registry. Do I need  
to put the FQDN and port number or just FQDN? For example,  
[portus.domain.com:5000](http://portus.domain.com:5000) ?

2. For the profiles, does the git path require no authentication? It is  
not clear how I should authenticate to my git repository?

3. Where can I find the logs? I only see in the Events \> Pending of the  
Container Build host that the action has not yet been picked up (it  
never gets picked up so I assume I did something wrong)

Thanks

---

<div class="post-metadata">

### Author: ![kwk](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/kwk/32/11997_2.png) [@kwk](https://forums.suse.com/u/kwk)
#### Post date: [November 15, 2017, 11:18am UTC](https://forums.suse.com/t/docker-suse-manager/29863/10 "2017-11-15T11:18:37Z")

</div>

Looks like you’ve asked this through multiple channels … :-/

We will update [https://wiki.microfocus.com/index.php/SUSE\_Manager/imagebuilding](https://wiki.microfocus.com/index.php/SUSE_Manager/imagebuilding) with all required information.

---

<div class="post-metadata">

### Author: ![so\_it\_team](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@so\_it\_team](https://forums.suse.com/u/so_it_team)
#### Post date: [November 15, 2017, 1:31pm UTC](https://forums.suse.com/t/docker-suse-manager/29863/11 "2017-11-15T13:31:23Z")

</div>

OK great thanks, I see that work has already started to update the wiki

---

<div class="post-metadata">

### Author: ![so\_it\_team](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@so\_it\_team](https://forums.suse.com/u/so_it_team)
#### Post date: [November 15, 2017, 4:18pm UTC](https://forums.suse.com/t/docker-suse-manager/29863/12 "2017-11-15T16:18:04Z")

</div>

Great, i have it working now…

For anyone else who needs the same answers:

1. Registry URL must contain port and the namespace

2. this format: [https://gitlab-ci-token:XXXXXXXXXX@gitlab.example.com/johndoe/myrepo.git#master:/images/slesbasic/](https://gitlab-ci-token:XXXXXXXXXX@gitlab.example.com/johndoe/myrepo.git#master:/images/slesbasic/)

3. rhn/rhn\_web\_ui.log rhn/rhn\_taskomatic\_daemon.log and salt/master or salt/api
