New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pipeline - unable to build in docker #178
Labels
Comments
1 task
I am running into a similar issue with github actions. I ran into this on localhost ubuntu 20.04 as well, but was able to work-around it by running apply twice, the first would always fail and the second would work. |
I created #352 which makes it possible to handle volume problems. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I have a CI/CD pipeline created in Bitbucket. I want to create a package (build in docker) and deploy it. However I am getting the following issue (might apply to Github actions as well):
This means that docker command is trying to access folder not available in bitbucket pipeline. Locally on my laptop it is working without any issues.
When I did a small code check I can see in package.py that you are always adding this inpiut into docker_cmd
https://github.com/terraform-aws-modules/terraform-aws-lambda/blob/master/package.py#:~:text=home%20%3D%20os.environ,%5D)
However for cases when you don't want to use SSH including .ssh/known_hosts is not required correct?
Before you submit an issue, please perform the following first:
.terraform
directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!):rm -rf .terraform/
terraform init
Versions
1.0.1
provider registry.terraform.io/hashicorp/aws v3.45.0
provider registry.terraform.io/hashicorp/external v2.1.0
provider registry.terraform.io/hashicorp/local v2.1.0
provider registry.terraform.io/hashicorp/null v3.1.0
provider registry.terraform.io/hashicorp/random v3.1.0
provider registry.terraform.io/kreuzwerker/docker v2.14.0
2.7.0
Reproduction
Steps to reproduce the behavior:
NOCode Snippet to Reproduce
Expected behavior
It should be able to build the package and deploy the software to AWS. Locally working without any issues.
Actual behavior
Terminal Output Screenshot(s)
Additional context
The text was updated successfully, but these errors were encountered: