-
Notifications
You must be signed in to change notification settings - Fork 69
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
Running in WSL on Windows 10 #3
Comments
Hey @theforgottenmachine , Thanks for the reply. Can you please confirm that you are using the last version of this repository? The thing that makes me wonder is the second output. The logfile indicates, that the Apistar Dockerfile is build in 4 steps - but it should be 8 steps as declared in the Apistar Dockerfile |
@jgoerner - Thank you for the reply! This only happens after I've run it once. The first time I get all eight steps: docker-compose build apistar
Everything looks good till it gets here:
Here's the result of docker-compose up (I didn't use -d so I could see the output):
The directory '/home/jovyan/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
I don't really know much about docker so I don't know stuff to modify. The first thing I noticed was on Step 3/4 where it talks about the directory. The error shows up after gunicorn starts and a worker thread hits the ModuleNotFoundError. Any ideas? |
Just wanted to add to this. I have now tried the same steps on a Mac and on an Ubuntu install. They both work great. The warning re. the home directory still came up. But the difference was that starting apistar just generated a line of output. It's this ModuleNotFoundError that is throwing me off. Maybe it could have something to do with the paths specified in the docker-compose file? @jgoerner thank you! |
Hi,
I'm trying to get this up and running using the Windows Subsystem for Linux. Three of the containers keep restarting. After debugging a little bit I found the following during the docker-compose build up step
Another thing that might be relevant was this (when I ran docker-compose build apistar):
Any ideas?
The text was updated successfully, but these errors were encountered: