Container uuid is invalid on updating a container with update redeploy

[ael-g]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Command attempted

scw container container update $CONTAINER_UUID registry-image=$IMAGE --wait redeploy

Expected Behavior

Container is updated to $IMAGE if it starts or stays on latest valid image otherwise

Actual Behavior

In case purposely using a non-starting image to test the redeploy behaviour, in the web console I see the container tries to start on the new image, stays in Deploying state for a bit, then I got

Failed to deploy this container
internal error

on the web console, the container service stays on the falty image and on the cli I got

Container uuid is invalid

More info

scw version
Version          2.42.0
BuildDate        unknown
GoVersion        go1.24.5
GitBranch        unknown
GitCommit        unknown
GoArch           arm64
GoOS             darwin
UserAgentPrefix  scaleway-cli

[remyleone]

Hello 👋 and thanks for opening an issue :) Could you provider the logs with the --debug option?

[ael-g]

Sure :)
I've removed some company-related data but can provide privately if necessary

container-debug-scaleway.log

[RemyMach]

Hello,
It seems that the issue with redeploying your new image is related to the incident we encountered this morning, which made image pulls impossible.
Feel free to check Scaleway’s public status page or join our Slack community to be notified as quickly as possible about this kind of issue.

You should now be able to redeploy new images without any issues.

[ael-g]

Thanks for you reply.
I just tried again but got the error again :

HTTP/2.0 400 Bad Request
Content-Length: 39
Content-Security-Policy: default-src 'none'; frame-ancestors 'none'
Content-Type: application/json
Date: Wed, 08 Oct 2025 13:56:02 GMT
Server: Scaleway API Gateway (fr-par-2;edge03)
Strict-Transport-Security: max-age=63072000
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-Request-Id: 2e3d8894-8c26-4292-bc74-a2b1c681ba3a

{"message":"container uuid is invalid"}
----------------------------------------------------------
Container uuid is invalid
version was already checked during past 24 hours

=> 15:56 Paris time

[ael-g]

Do you have any news about the issue? Thanks

[Mia-Cross]

Hello @ael-g,
I've had a hard time figuring out what was wrong but I finally did ! The argument redeploy is a boolean so it should be set with redeploy=true (or you can just drop it because its default value is true). With the way you set it, the CLI interprets the word redeploy as a positional argument, so as a container uuid.
Sorry that it took so long to notice this detail... Let me know if that does not fix the issue for you !