On Tue, Jun 2, 2020 at 7:28 AM Arthur Smith <arthurpsm...@gmail.com> wrote: > > and I can see I should use the image > docker-registry.tools.wmflabs.org/toolforge-python37-web > (by the way, docker-registry.toolforge.org does NOT work right now when > fetching images!)
docker-registry.toolforge.org is a tool for browsing the registry, not a registry itself. The registry is found at https://docker-registry.tools.wmflabs.org as shown in the image name that you referenced. > but I can't figure out how to tell the image where to find the python app in > the docker start command. Any hints out there? These containers do not really work the way that a typical Docker image would. The `webservice` command manipulates them at runtime in various ways for boring legacy compatibility reasons. For a Python runtime, the `webservice-runner` component which is started inside the container runs /usr/bin/uwsgi with a lot of configuration [0]. You could figure out something that works for you to run the uwsgi container in a different manner. The community contributed documentation that you have found for running lighttpd really has no relation to how the PHP containers are actually used by `webservice`. [0]: https://gerrit.wikimedia.org/r/plugins/gitiles/operations/software/tools-webservice/+/master/toolsws/wstypes/uwsgi.py#18 Bryan -- Bryan Davis Technical Engagement Wikimedia Foundation Principal Software Engineer Boise, ID USA [[m:User:BDavis_(WMF)]] irc: bd808 _______________________________________________ Wikimedia Cloud Services mailing list Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/cloud
