So the wordpress_docker.zip merely contains the assets for the build job - it uses this to build the container and push it into ECR within the same region. You should see two containers there, one tagged base (which is the uncustomized docker image) and one tagged latest, which is the result of the CodeBuild job. With this present you should be able to launch the Wordpress container.
If you are still experiencing issues, please feel free to raise an issue on GitHub with some more information about your set-up and I can investigate.
Also I am was able to verify that the task is running the latest image (241712483418.dkr.ecr.us-east-2.amazonaws.com/viajesconanto-serverless-wordpress:latest).
So my guess is that the image is throwing the "no such file or directory" error.
I will report this problem (major one that does not allow me to continue). Also I have find minor other ones, like:
The aws route53domains command lacks of two spaces (typo) between each of the Name=${} definitions.
The password override defined for the RDS Aurora server contains the illegal "@".
The terraform module only can be executed in regions that support RDS Aurora Server with Serverless option provisioned. I tried to launch it in South America (Sao Pablo) wich lacks of it.
The docker push command when running from windows lacks of double quotes escaping so when ".terraform" path tried to be executed the cli understands is trying to run that executable.
So the wordpress_docker.zip merely contains the assets for the build job - it uses this to build the container and push it into ECR within the same region. You should see two containers there, one tagged base (which is the uncustomized docker image) and one tagged latest, which is the result of the CodeBuild job. With this present you should be able to launch the Wordpress container.
If you are still experiencing issues, please feel free to raise an issue on GitHub with some more information about your set-up and I can investigate.
Yeah, I'm seeing both. The base one was generated about 5 minutes before than the latest one: dev-to-uploads.s3.amazonaws.com/up...
Also I am was able to verify that the task is running the latest image (241712483418.dkr.ecr.us-east-2.amazonaws.com/viajesconanto-serverless-wordpress:latest).
So my guess is that the image is throwing the "no such file or directory" error.
I will report this problem (major one that does not allow me to continue). Also I have find minor other ones, like:
Thank you, your feedback to track as an issue would be welcomed!