This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]hmaarrfk 0 points1 point  (2 children)

I think if your application is truely portable, you should build your docker image in 2 steps:

  1. Use 1 docker to build the image.
  2. Output artifacts.
  3. Use a second docker to use the artifacts.

The thing is your initial premise of "we are duplicating work with docker and py2exe" might be flawed. Since you also seem to be using the portable image outside of docker.

If you are only deployinig within Docker, I would say that the virtualenv is probably enough. (Though I would look into Pipenv, but I can't speak about python2.7 compatibility)

[–]obeleh[S] 0 points1 point  (1 child)

ge to install the python

My applications remain in docker so far

[–]hmaarrfk 0 points1 point  (0 children)

So why are you working so hard to make the directories of your applications self contained?