What's the right --image argument for toolforge-jobs to get a python3.11 backend?
I'm getting: Value error, No such image 'tf-python311' when I do:
toolforge-jobs run add-tags-en --command $jobdir/add-tags-en.bash --image tf-python311--schedule "*/5 * * * *"
On Wed, Jan 22, 2025 at 3:50 AM Roy Smith roy@panix.com wrote:
What's the right --image argument for toolforge-jobs to get a python3.11 backend?
This was already answered in IRC (thanks JJMC89!), I'm copying it here in case it's useful for somebody else:
03:55 <JJMC89> roy649: its python3.11 -- the tf- prefix isn't used any more and the alias only exists for the older images 03:57 <JJMC89> https://wikitech.wikimedia.org/wiki/Module:Toolforge_images/data.json is the onwiki info about the images
On 01/21 21:50, Roy Smith wrote:
What's the right --image argument for toolforge-jobs to get a python3.11 backend?
I'm getting: Value error, No such image 'tf-python311' when I do:
toolforge-jobs run add-tags-en --command $jobdir/add-tags-en.bash --image tf-python311--schedule "*/5 * * * *"
That'd be python3.11, you can see all the pre-built images available running:
$ toolforge jobs images
Another option is building your project using the build-service [1], you'll need to have your code in a public git repository (like gitlab.wikimedia.org). That will also allow you soon-ish to deploy your code when it changes (push to deploy), and you'll get support for more runtimes, and better control of your running environment.
https://wikitech.wikimedia.org/wiki/Help:Toolforge/Building_container_images...
Cloud mailing list -- cloud@lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/
The webservice command has better handling, listing the valid images:
$ webservice xxx shell type must be one of: bookworm * buildservice * jdk17 * node16 * node18 * perl5.32 * perl5.36 * php7.4 * php8.2 * python3.11 * python3.9 * ruby2.1 * ruby2.7 * ruby3.1 * tcl8.6
-- SD0001
On Wed, 22 Jan 2025 at 14:18, David Caro dcaro@wikimedia.org wrote:
On 01/21 21:50, Roy Smith wrote:
What's the right --image argument for toolforge-jobs to get a python3.11
backend?
I'm getting: Value error, No such image 'tf-python311' when I do:
toolforge-jobs run add-tags-en --command $jobdir/add-tags-en.bash
--image tf-python311--schedule "*/5 * * * *"
That'd be python3.11, you can see all the pre-built images available running:
$ toolforge jobs images
Another option is building your project using the build-service [1], you'll need to have your code in a public git repository (like gitlab.wikimedia.org). That will also allow you soon-ish to deploy your code when it changes (push to deploy), and you'll get support for more runtimes, and better control of your running environment.
https://wikitech.wikimedia.org/wiki/Help:Toolforge/Building_container_images...
Cloud mailing list -- cloud@lists.wikimedia.org List information:
https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/
-- David Caro SRE - Cloud Services Wikimedia Foundation https://wikimediafoundation.org/ PGP Signature: 7180 83A2 AC8B 314F B4CE 1171 4071 C7E1 D262 69C3
"Imagine a world in which every single human being can freely share in the sum of all knowledge. That's our commitment." _______________________________________________ Cloud mailing list -- cloud@lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/