# container-suseconnect does not work on EC2 base images

**URL:** <https://forums.suse.com/t/container-suseconnect-does-not-work-on-ec2-base-images/30504>\
**Category:** Amazon-EC2\
**Created:** [November 3, 2017, 10:37pm UTC](https://forums.suse.com/t/container-suseconnect-does-not-work-on-ec2-base-images/30504 "2017-11-03T22:37:58Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![gregmeyer](https://avatars.discourse-cdn.com/v4/letter/g/ed655f/32.png) [@gregmeyer](https://forums.suse.com/u/gregmeyer)\
**Post date:** [November 3, 2017, 10:37pm UTC](https://forums.suse.com/t/container-suseconnect-does-not-work-on-ec2-base-images/30504/1 "2017-11-03T22:37:58Z")

</div>

I installed docker and the image. I activated the image with sle2docker. I started the container, and tried to do stuff in it. However, it is always failing when I try to refresh the package repos.

`ec2-user@ip-172-31-32-162:~> docker run --rm -it suse/sles11sp4-docker bash
bash-3.2# zypper ref
Refreshing service 'container-suseconnect'.
Problem retrieving the repository index file for service 'container-suseconnect':
[|]
Skipping service 'container-suseconnect' because of the above error.
There are no enabled repositories defined.
Use 'zypper addrepo' or 'zypper modifyrepo' commands to add or enable repositories.`

SUSE connect says that the container module is installed:

[CODE]ec2-user@ip-172-31-32-162:~\> sudo SUSEConnect --list-extensions  
AVAILABLE EXTENSIONS AND MODULES

FREE EXTENSIONS

Toolchain Module 12 x86\_64 (Installed)  
De-Install with: SUSEConnect -d -p sle-module-toolchain/12/x86\_64

Legacy Module 12 x86\_64 (Installed)  
De-Install with: SUSEConnect -d -p sle-module-legacy/12/x86\_64

HPC Module 12 x86\_64 (Installed)  
De-Install with: SUSEConnect -d -p sle-module-hpc/12/x86\_64

Advanced Systems Management Module 12 x86\_64 (Installed)  
De-Install with: SUSEConnect -d -p sle-module-adv-systems-management/12/x86\_64

Web and Scripting Module 12 x86\_64 (Installed)  
De-Install with: SUSEConnect -d -p sle-module-web-scripting/12/x86\_64

SUSE Package Hub 12 SP3 x86\_64 (Installed)  
De-Install with: SUSEConnect -d -p PackageHub/12.3/x86\_64

Containers Module 12 x86\_64 (Installed)  
De-Install with: SUSEConnect -d -p sle-module-containers/12/x86\_64

SUSE Linux Enterprise Software Development Kit 12 SP3 x86\_64 (Installed)  
De-Install with: SUSEConnect -d -p sle-sdk/12.3/x86\_64

Public Cloud Module 12 x86\_64 (Installed)  
De-Install with: SUSEConnect -d -p sle-module-public-cloud/12/x86\_64

MORE INFORMATION

You can find more information about available modules here:  
[https://www.suse.com/products/server/features/modules.html[/CODE]](https://www.suse.com/products/server/features/modules.html%5B/CODE%5D)

And the images themselves install and activate just fine.

So, what am I doing wrong? Does anyone have any advice for me? zypper works on the host system, just not on the containers.

---

<div class="post-metadata">

**Author:** ![Automatic\_Reply](https://avatars.discourse-cdn.com/v4/letter/a/ecb155/32.png) [@Automatic\_Reply](https://forums.suse.com/u/Automatic_Reply)\
**Post date:** [November 8, 2017, 7:30am UTC](https://forums.suse.com/t/container-suseconnect-does-not-work-on-ec2-base-images/30504/2 "2017-11-08T07:30:35Z")

</div>

gregmeyer,

It appears that in the past few days you have not received a response to your  
posting. That concerns us, and has triggered this automated reply.

These forums are peer-to-peer, best effort, volunteer run and that if your issue  
is urgent or not getting a response, you might try one of the following options:

- Visit [http://www.suse.com/support](http://www.suse.com/support) and search the knowledgebase and/or check all  
the other support options available.
- Open a service request: [https://www.suse.com/support](https://www.suse.com/support)
- You could also try posting your message again. Make sure it is posted in the  
correct newsgroup. ([http://forums.suse.com](http://forums.suse.com))

Be sure to read the forum FAQ about what to expect in the way of responses:  
[http://forums.suse.com/faq.php](http://forums.suse.com/faq.php)

If this is a reply to a duplicate posting or otherwise posted in error, please  
ignore and accept our apologies and rest assured we will issue a stern reprimand  
to our posting bot…

Good luck!

Your SUSE Forums Team  
[http://forums.suse.com](http://forums.suse.com)

---

<div class="post-metadata">

**Author:** ![enovaklbank](https://avatars.discourse-cdn.com/v4/letter/e/aca169/32.png) [@enovaklbank](https://forums.suse.com/u/enovaklbank)\
**Post date:** [September 27, 2018, 5:25pm UTC](https://forums.suse.com/t/container-suseconnect-does-not-work-on-ec2-base-images/30504/3 "2018-09-27T17:25:09Z")

</div>

Sorry for the necro but I’ve just found this thread via google while searching for the same error message. I figured it out since then, so for anyone in the same shoes: you need to add the certificates/CAs to the image and trust them.

`# Import the crt file of our private SMT server
ADD http://smt.test.lan/smt.crt /etc/pki/trust/anchors/smt.crt
RUN update-ca-certificates`

---

<div class="post-metadata">

**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\
**Post date:** [September 27, 2018, 7:25pm UTC](https://forums.suse.com/t/container-suseconnect-does-not-work-on-ec2-base-images/30504/4 "2018-09-27T19:25:45Z")

</div>

Hi enovaklbank,

> Sorry for the necro

no need to be sorry - solutions are always welcome, thank you for providing one!

Regards  
J
