can you not pass envVars with startAndWaitForPorts?
can you not pass envVars with startAndWaitForPorts?
start, but looks like it will default to the container-level envVars so you could set them there


start method so that I can provide a JOB_ID environment variable to the container. The job starts up and begins processing for roughly 2 minutes before dying? Is this normal? Btw I'm setting the sleepAfter option to 24hError: Container is not enabled for this durable object class. Have you correctly setup your wrangler.toml?max_instances or updating to a basic / standard instance_type 

startstartenvVarsJOB_IDsleepAfter24h => => naming to registry.cloudflare.com/b6e9a2ec6a599a3fec8a63f9fc29c03d/browsershot-containers:22743b05 0.0s
Login Succeeded
Image does not exist remotely, pushing: registry.cloudflare.com/b6e9a2ec6a599a3fec8a63f9fc29c03d/browsershot-containers:22743b05
The push refers to repository [registry.cloudflare.com/b6e9a2ec6a599a3fec8a63f9fc29c03d/browsershot-containers]Error: Container is not enabled for this durable object class. Have you correctly setup your wrangler.toml?max_instancesinstance_type