The script file is in a sub-directory (called "Middleware"), so the
Dockerfile CMD is CMD ["Middleware/c3stemserver.py"].
The script does modify sys.path. This line is in the script before the
import sys.path.append('/opt/C3STEM/Middleware/').
On Friday, November 20, 2015 at 3:06:44 PM UTC-6, Graham Dumpleton wrote:
>
> Which directory is the wsgi script file in? The top level directory of
> your project or a sub directory?
>
> What do you have for the CMD in your Dockerfile?
>
> Does your WSGI script file attempt to make modifications to sys.path in
> any way?
>
> Graham
>
> On 21 Nov 2015, at 3:43 AM, Collin Jackson <[email protected]
> <javascript:>> wrote:
>
> I initially wrote a couple of replies to your comments, but I discovered
> some additional important information, so I just deleted those and decided
> to start over instead of cluttering the response chain.
>
> I'm new to the code base I'm working with and didn't realize that the
> ImportError was being thrown for an include of a local file, not a package
> (so sorry for the confusion). The file to be imported is in the same
> directory as the wsgi script. Does the wsgi script get copied to another
> directory before running?
>
> On Friday, November 20, 2015 at 4:31:24 AM UTC-6, Graham Dumpleton wrote:
>>
>> Sorry for separate messages and not adding to discussion. Don't mean to
>> confuse you. Best I can do right now.
>>
>> If your Dockerfile has USER line in it try commenting it out.
>>
>> This is not a permanent solution but will help isolate whether is
>> permissions issue on writing to application code directory
>>
>> Graham
>>
>> On 20 Nov 2015, at 2:34 PM, Collin Jackson <[email protected]> wrote:
>>
>> I'm running mod-wsgi-docker:python-2.7-onbuild and have listed my
>> requirements in requirements.txt. During build, I can see that the packages
>> are installed properly, but when I try to run the image, it crashes on the
>> first non-Standard Library import with an ImportError exception. I can't
>> figure out what's happening and it's not exactly easy to poke around inside
>> the container to see what's going on. I noticed that a virtual environment
>> is created prior to installing the packages (here
>> <https://github.com/GrahamDumpleton/mod_wsgi-docker/blob/master/2.7/build.sh#L87>),
>>
>> but I imagine that if this is the issue, other users would have the same
>> issue. Any ideas?
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "modwsgi" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To post to this group, send email to [email protected].
>> Visit this group at http://groups.google.com/group/modwsgi.
>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "modwsgi" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected] <javascript:>.
> To post to this group, send email to [email protected] <javascript:>
> .
> Visit this group at http://groups.google.com/group/modwsgi.
> For more options, visit https://groups.google.com/d/optout.
>
>
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.
