Sidebar navigationMain contentFooter
Jump toSuggest an edit

Common errors encountered while using Serverless Containers

Reviewed on 24 August 2023Published on 24 August 2023

Unable to deploy the image

Possible solutions

  • Make sure that the image used contains a valid web server (Nginx, Apache, etc.).

  • Make sure the container is bound to 0.0.0.0.

  • Make sure the container is listening on port $PORT or 8080.

  • Check if pods are in CrashLoopBackOff status.

  • Make sure you built your image for an amd64 architecture, as arm64 is not supported.

  • Make sure your deployment does not exceed the limitations of Serverless Containers.

    Tip

    Run the docker inspect command to get detailed information on your image:

    docker inspect myimage

Unable to build

Possible solutions

  • Make sure that you used a public image from the Docker Registry or a compatible image from the Scaleway Container Registry.

  • Make sure the image is still available in the Scaleway Container Registry.

Failed to create a namespace

Cause

This issue can happen for the following reasons:

  • You created too many namespaces and reached your account’s quota
  • You created too many Registry namespaces and reached your account’s quota

Possible solutions

Make sure that you did not exceed the maximum number of allowed namespaces with the Scaleway console or with the API.

Cloud Products & Resources
  • Scaleway Console
  • Compute
  • Storage
  • Network
  • IoT
  • AI
Dedicated Products & Resources
  • Dedibox Console
  • Dedibox Servers
  • Network
  • Web Hosting
Scaleway
  • Scaleway.com
  • Blog
  • Careers
  • Scaleway Learning
Scaleway Docs
Follow us
FacebookTwitterSlackInstagramLinkedin
ContractsLegal NoticePrivacy PolicyCookie PolicyDocumentation license
© 1999-2024 – Scaleway SAS