I see that the logs you shared hasn't been completed. It may be that deployment is still ongoing or canceled.
You should refresh the logs after some time. If you see similar message below, it means the deployment failed.
[18/Sept/2022:08:48:26] [deployment:1] Canceled
I can see that you are running kalilinux/kali-rolling. Note that this is unlike a web based application image that exposes container ports for it to be in running state.
Did you provide any launch command for this Kali linux image in the Lightsail deployment? I did inspect the image and I see that you can run bash commands with it during startup.
docker inspect kalilinux/kali-rolling | grep Cmd -A2 "Cmd": [ "bash" ],
If you create the deployment in Lightsail without a launch command that ought to keep the container in a running state, the container will fail, hence the error you faced.
To resolve this, specify a Launch command for example
tail -f /dev/null that will ensure the container remain in running state then your deployment will succeed as the container will return the message: "Reached a steady state".
Refer to more example here.
Thank you for your response.
Lightsail container as CloudFront Origin returns 404 No Such ServiceAccepted Answerasked 7 months ago
Lambda container and oci image manifest typeasked 3 months ago
cant ssh from linux kali to my lightsail ubuntuasked a year ago
How to deploy Amazon Linux on a Lightsail Container Service?Accepted Answer
LOGIN INTO LINUX KALI EC2 INSTANCE FAILUREasked 5 months ago
How to create Kali Linux container on LightSailasked 12 days ago
Lightsail Container Linux Deployment fails
Migrating Multi-container Docker running on Amazon Linux to ECS on Amazon Linux 2asked 6 months ago
How to export tresained models to ECR as container imageAccepted Answerasked 14 days ago
Can I attach Lightsail disk to a Lightsailt container?Accepted Answerasked 7 months ago