Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(cr): add troubleshooting #4557

Merged
merged 5 commits into from
Mar 10, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions menu/navigation.json
Original file line number Diff line number Diff line change
Expand Up @@ -2234,6 +2234,16 @@
],
"label": "API/CLI",
"slug": "api-cli"
},
{
"items": [
{
"label": "Common errors when pushing images to Container Registry",
"slug": "common-errors-when-pushing-images-to-container-registry"
}
],
"label": "Troubleshooting",
"slug": "troubleshooting"
}
],
"label": "Container Registry",
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,73 @@
---
meta:
title: Common errors when pushing images to Container Registry
description: Solutions for resolving issues when pushing images to Scaleway's Container Registry.
content:
h1: Common errors when pushing images to Container Registry
paragraph: This guide provides solutions for common issues encountered when pushing images to Scaleway's Container Registry.
tags: container-registry, troubleshooting
dates:
validation: 2025-03-05
posted: 2025-03-05
categories:
- container-registry
---

## Problem
You are unable to push images to Scaleway's Container Registry.

### Symptoms
- The `docker push` command fails with an error message.
- Authentication or authorization errors occur.
- The image push process hangs or times out.

## Possible causes
- Incorrect authentication or authorization settings.
- Misconfigured or outdated Docker client.
- Network connectivity issues or firewall restrictions.
- Exceeded Container Registry quotas or limits.

## Solutions

### Verify authentication and authorization
- Ensure you are logged in with a valid Scaleway account using `docker login`.
- Confirm that your account has the necessary permissions to push images.
- Verify that your Docker client is [correctly configured](/container-registry/how-to/connect-docker-cli/) for Scaleway's Container Registry.

### Review error messages and logs
- Run the push command with verbose output for more details:
```sh
docker push --debug <your-image>
```
- Check the Docker client logs for warnings or errors:
```sh
docker logs <container_id>
```
- Verify Scaleway’s Container Registry [status](https://status.scaleway.com/) for any ongoing incidents.

### Check Docker configuration and version
- Ensure your Docker client is up-to-date by running:
```sh
docker --version
```
- Check for configuration errors in the Docker daemon and client.
- Review the [Docker documentation](https://docs.docker.com/) for known compatibility issues.

### Investigate network connectivity issues
- Confirm that your internet connection is stable.
- Check firewall or proxy settings that may be blocking the connection.
- Try pushing the image from a different network or VPN to rule out local issues.

### Verify Container Registry quotas and limits
- Ensure you have not exceeded your Scaleway Container Registry storage limits.
- Refer to Scaleway’s documentation for [quota information](/organizations-and-projects/additional-content/organization-quotas/#container-registry).

## Additional troubleshooting steps
- Try pushing a small test image to verify general functionality:
```sh
docker pull alpine && docker tag alpine <your-registry>/test-image && docker push <your-registry>/test-image
```
- Review Docker’s official [troubleshooting guides](https://docs.docker.com/tags/troubleshooting/) for further insights.
- If the issue persists, [contact our support team](https://console.scaleway.com/support) with error logs and diagnostic details.