---
title: "Error Message during Container Installation"
slug: "error-message-during-container-installation"
updated: 2024-12-13T07:36:06Z
published: 2025-02-11T14:51:55Z
canonical: "docs.telosalliance.com/error-message-during-container-installation"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.telosalliance.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Error Message during Container Installation

When installing a containerized Telos product such as iQ/s, VX/s, etc. you may see this error during the installation process:

```plaintext
unauthorized: access to the requested resource is not authorized
```

This happens when access is denied to your repository on Quay.io.

The most common causes are that the Quay username is incorrect, or you have not been added to the repository by our activation team. If your username does not fit the format of our guidelines, then we will not be able to activate your product.

see: [https://docs.telosalliance.com/docker-deployment/quay.io](https://docs.telosalliance.com/docker-deployment/quay.io)

Per the guide, when creating the username in Quay.io the customer needs to make sure the username matches the following format: `yourcompanyname_yourfirstname_yourlastname`.

Once you have created a supported username you can register your product here: [https://success.telosalliance.com/iqs-register](https://success.telosalliance.com/iqs-register)

Then after you've been added to the correct repository, you may complete the installation of the product.

> [!CAUTION]
> **STOP!** If you need to run the installation script for again to finish the installation, please follow these instructions for removing the failed installation before running the install script again:
> 
> [https://support.telosalliance.com/article/4kld5h3fhk-removing-unwanted-docker-compose-containers](/article/4kld5h3fhk-removing-unwanted-docker-compose-containers)

## Let us know how we can help

If you have further questions on this topic or have ideas about improving this document, please [contact us](/docs/contact).