Skip to content
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

ModuleNotFoundError using Docker Image #97

Closed
anthonycolon25 opened this issue Jun 21, 2019 · 4 comments
Closed

ModuleNotFoundError using Docker Image #97

anthonycolon25 opened this issue Jun 21, 2019 · 4 comments
Assignees
Labels

Comments

@anthonycolon25
Copy link

I was trying to test out the new 1.0.0 version. I figured I would go the simple route and just use the docker image. When I run the instructions below (per the Usage instructions) I get the following.

$ function terraform-compliance { docker run --rm -v $(pwd):/target -i -t eerkunt/terraform-compliance "$@"; }
$ terraform-compliance -h
Unable to find image 'eerkunt/terraform-compliance:latest' locally
latest: Pulling from eerkunt/terraform-compliance
fc7181108d40: Pull complete
01f3b6f74410: Pull complete
d8e6069e053d: Pull complete
e6bd64ad4fe3: Pull complete
a034e22b86de: Pull complete
8731bd654de0: Pull complete
Digest: sha256:a53c917fd3c0f4ee3a7fdfe6a5a14d32410f01b99ba5a782520d17d2f9506486
Status: Downloaded newer image for eerkunt/terraform-compliance:latest
Traceback (most recent call last):
File "/usr/local/bin/terraform-compliance", line 6, in
from terraform_compliance.main import cli
File "/usr/local/lib/python3.6/site-packages/terraform_compliance/main.py", line 7, in
from terraform_compliance.common.readable_plan import ReadablePlan
File "/usr/local/lib/python3.6/site-packages/terraform_compliance/common/readable_plan.py", line 5, in
import filetype
ModuleNotFoundError: No module named 'filetype'

Is this an issue with the docker image? If not, please let me know if I may be missing anything on my MacBook.

@eerkunt eerkunt self-assigned this Jun 21, 2019
@eerkunt eerkunt added bug fixing A fix is addressed, no further data is required labels Jun 21, 2019
@eerkunt
Copy link
Member

eerkunt commented Jun 21, 2019

Thanks for reporting! This was a global problem. Just added filetype to the packaging setup.

eerkunt added a commit that referenced this issue Jun 21, 2019
…st-in-setup

## 1.0.1 (2019-06-21)
* Fixed an issue where `filetype` module could not be found. (#97)
* Upgraded python in Docker image from 3.6.8 to 3.7.3
@eerkunt
Copy link
Member

eerkunt commented Jun 21, 2019

Could you please try with 1.0.1 version ?

@anthonycolon25
Copy link
Author

anthonycolon25 commented Jun 21, 2019

Just tested with 1.0.1. Error is gone and I now get the help information.

Thx.

@eerkunt eerkunt removed the fixing A fix is addressed, no further data is required label Jun 21, 2019
@eerkunt
Copy link
Member

eerkunt commented Jun 21, 2019

Thanks for the quick validation! Closing the issue.

@eerkunt eerkunt closed this as completed Jun 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants