# Suma 5.02: Image building with gitlab

**URL:** <https://forums.suse.com/t/suma-5-02-image-building-with-gitlab/45116>\
**Category:** SUSE Multi Linux Manager\
**Created:** [February 11, 2025, 2:06pm UTC](https://forums.suse.com/t/suma-5-02-image-building-with-gitlab/45116 "2025-02-11T14:06:04Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![StefanS1](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/stefans1/32/12008_2.png) [@StefanS1](https://forums.suse.com/u/StefanS1)\
**Post date:** [February 11, 2025, 2:06pm UTC](https://forums.suse.com/t/suma-5-02-image-building-with-gitlab/45116/1 "2025-02-11T14:06:05Z")

</div>

Hello,  
I am on **SuSE Manager 5.0.2 Server** on a vm no. **srv181**.  
Also installed a current **gitlab 17.8 c** e on another vm **srv184**.  
And installed **sles 15 sp6 as build host** for SuSE Manager on vm **srv183**.

On vm no. 3 i have successfully configured docker, to build via Dockerfile a working container. That image i have tagged and pushed to the gitlab docker registry:

```auto
docker tag my-apache2 srv184.linux.lab:5050/suma/suma_repository/my-apache2
docker push srv184.linux.lab:5050/suma/suma_repository/my-apache2

srv183:~/http_dockerfile # docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
my-apache2 latest 59290484845d 41 minutes ago 148MB
srv184.linux.lab:5050/suma/suma_repository/my-apache2 latest 59290484845d 41 minutes ago 148MB
httpd 2.4 4d98e80840bb 2 weeks ago 148MB

```

 ![gitlab_docker_image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/e/eebda31fdb845f58cf7c4f03fd6e4b03c0a0478b.png)

So far the environment underneath. Now configured the SuSE Manager Image Section:

 ![suma_image_store](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/6/62ebe53e1795cf39c633d10500ce087d83f89b2d.png)

 ![suma_image_profile](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/a/ac8d6d31b0594aa09e2d08f3f799c9a2d78e7314.png)

And here the “Dockerfile”:

```auto
FROM httpd:2.4

```

```auto
----------
          ID: mgr_registries_login
    Function: mgrcompat.run
        Name: docker.login
      Result: true
     Comment: Module function docker.login executed
     Started: 14:44:03.129290
    Duration: 222.647
         SLS: images.docker
     Changed: ret:
                  retcode: 0.0
                  Errors: [
                      ]
                  Results:
                      srv184.linux.lab:5050/suma/suma_repository: true
              
----------
          ID: mgr_buildimage
    Function: mgrcompat.run
        Name: docker.build
      Result: false
     Comment: Module function docker.build threw an exception. Exception: invalid tag 'srv184.linux.lab:5050/suma/suma_repository/apache:latest': invalid reference format
     Started: 14:44:03.352298
    Duration: 4.048
         SLS: images.docker
     Changed: {}
----------

```

But the build failed, and I do not know why it fails.  
Please give me support in solving it. Thank you.

Best regards  
Stefan

---

<div class="post-metadata">

**Author:** ![StefanS1](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/stefans1/32/12008_2.png) [@StefanS1](https://forums.suse.com/u/StefanS1)\
**Post date:** [February 18, 2025, 8:09am UTC](https://forums.suse.com/t/suma-5-02-image-building-with-gitlab/45116/2 "2025-02-18T08:09:18Z")

</div>

Wow, no one, who has ever used that feature (container building) of suma and can give me instructions for using it? Even no SuSE employer here in it to support? 🙄

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [February 18, 2025, 12:35pm UTC](https://forums.suse.com/t/suma-5-02-image-building-with-gitlab/45116/3 "2025-02-18T12:35:16Z")

</div>

@StefanS1 Hi, then it’s probably better for you to create a support request on your issue.

---

<div class="post-metadata">

**Author:** ![StefanS1](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/stefans1/32/12008_2.png) [@StefanS1](https://forums.suse.com/u/StefanS1)\
**Post date:** [February 18, 2025, 1:40pm UTC](https://forums.suse.com/t/suma-5-02-image-building-with-gitlab/45116/4 "2025-02-18T13:40:53Z")

</div>

@malcolmlewis I am in a test period of suma, in order get a clue, what is functioning and what not. And the problem is so far, that test users are not able to get support via tickets…

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [February 18, 2025, 2:26pm UTC](https://forums.suse.com/t/suma-5-02-image-building-with-gitlab/45116/5 "2025-02-18T14:26:21Z")

</div>

@StefanS1 Well I’m not a Suma or docker user, but looking at this link you use the ID tag [https://docs.docker.com/reference/cli/docker/image/tag/](https://docs.docker.com/reference/cli/docker/image/tag/) not the URL?

---

<div class="post-metadata">

**Author:** ![StefanS1](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/stefans1/32/12008_2.png) [@StefanS1](https://forums.suse.com/u/StefanS1)\
**Post date:** [February 19, 2025, 8:43am UTC](https://forums.suse.com/t/suma-5-02-image-building-with-gitlab/45116/6 "2025-02-19T08:43:41Z")

</div>

@malcolmlewis When building, tagging and pushing via command line of the suma build host, all is fine.  
I do not have a clue, in which fields of the image store or the build config the misconfiguration lies in.  
I assume a lacking documentation of that feature, for example no screenshots of working configs are shown.

---

<div class="post-metadata">

**Author:** ![StefanS1](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/stefans1/32/12008_2.png) [@StefanS1](https://forums.suse.com/u/StefanS1)\
**Post date:** [March 11, 2025, 8:55am UTC](https://forums.suse.com/t/suma-5-02-image-building-with-gitlab/45116/7 "2025-03-11T08:55:36Z")

</div>

→ informing you, that the SuSE support worked out the problem and developed a TEST fix, that is working.
