They retain it for the lifetime of the container.
They retain it for the lifetime of the container.
Error checking if container is ready: The operation was abortedFailed to start container: The container is not running, consider calling start()
POST to /accounts/{account_id}/containers/registries/registry.cloudflare.com/credentials with { "expiration_minutes": 5, "permissions": [ "pull", "push" ] } in the body to generate tmp credentials, it will return stuff you can use in docker loginDataCloneError: Could not serialize object of type "DurableObjectNamespace". This type does not support serialization.console.log({ message: 'Some message' }), the output is pretty-printed and observability treats each line as a separate log, e.g."message": "{""message": "message: 'Some message'""message": "}""message": "{ message: 'Some message' }"process.stdout.write(JSON.stringify({ message: 'Some message' })) doesn't seem to emit any observability logs at all?? Am I doing something wrong?



stop() (or destroy()) then start() it again?startAndWaitForPorts

Error checking if container is ready: The operation was abortedFailed to start container: The container is not running, consider calling start()/accounts/{account_id}/containers/registries/registry.cloudflare.com/credentials{ "expiration_minutes": 5, "permissions": [ "pull", "push" ] }docker loginDataCloneError: Could not serialize object of type "DurableObjectNamespace". This type does not support serialization.Failed to start container: The container is not running, consider calling start()Failed to start container: The container is not running, consider calling start()console.log({ message: 'Some message' })"message": "{""message": "message: 'Some message'""message": "}""message": "{ message: 'Some message' }"process.stdout.write(JSON.stringify({ message: 'Some message' }))stop()destroy()start()startAndWaitForPorts await container.startAndWaitForPorts({
ports: [8080],
startOptions: {
enableInternet: true,
...c.env,
},
});