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

added Dockerfile #520

Closed
wants to merge 1 commit into from
Closed

added Dockerfile #520

wants to merge 1 commit into from

Conversation

robtec
Copy link

@robtec robtec commented Oct 3, 2016

Hi,

As I don't have a python development environment, I made a Dockerfile to build the latest.
Figured might be worth contributing it back to you guys

$ docker build -t robtec/molecule .
...
$ docker run -it robtec/molecule molecule --version
molecule, version 1.10.1.dev82

Initial thoughts?

Signed-off-by: Rob Powell rob@robpowell.engineering

Signed-off-by: Rob Powell <rob@robpowell.engineering>
@@ -0,0 +1,13 @@
FROM python:3.3
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FYI - Molecule is currently only python 2.7 compatible.

@retr0h
Copy link
Contributor

retr0h commented Oct 4, 2016

Hi @robtec, thanks for thinking of us and sending us a PR. I'm probably going to hold off on this, and get a feel for what other developers are doing. We haven't had any issues around this, and might cause confusion if we cannot support a molecule-docker workflow.

Also, to run a molecule development environment, it requires vagrant/virtualbox and docker as well.

Again, appreciate the PR, I'd just like to hold off for now.

@retr0h retr0h closed this Oct 4, 2016
@robtec
Copy link
Author

robtec commented Oct 4, 2016

Hey, yes this wouldn't play well with virtual box, would require a bind mount to the host docker sock for docker to work also.

Appreciate your feedback, thank you

apatard added a commit to apatard/molecule that referenced this pull request Apr 29, 2020
Since sh.py 1.13, a new check on the environment variables has been added
with commit amoffat/sh@5b27477.

This leads to failures in the testsuite since the code is passing
os.environ, which is not a dict().

It's also breaking MOLECULE_ENV_FILE handling with errors like (from the testsuite):

E           TypeError: Invalid special arguments:
E
E             'env': value None of env key 'MOLECULE_ENV_FILE' must be a str

so:
- use dict() to convert os.environ to a dict in _rebake_command(),
- use str() when defining MOLECULE_ENV_FILE to make sure self.env_file is a string.

To avoid any other surprise with 1.14 or newer, I've changed the sh.py requirement
to < 1.14. The requirement is not 1.13 but 1.13.1 to get the fix for sh.py bug ansible#520
(amoffat/sh#520).

Signed-off-by: Arnaud Patard <apatard@hupstream.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants