Artefact or container registry

[Sylvain Brohee]

Hi list,

We just set up ou whole genome analysis pipeline on Google Cloud (using nextflow) but we faced the issue that when using the option google.lifeSciences.usePrivateAddress, all our processes die with the following error :

exit code 9

Command error:

  The worker was unable to check in, possibly due to a misconfigured network

We suppose that this could be due to the fact we are using an artefact registry instead of a container registry as stated in the documentation. I was wondering if any of you already encountered this issue and / or whether there is a way to work with artefact registry nevertheless (which is the new way of the hosting at google).

Is any of you aware that this possibility could be added in the future?

Many thanks for your insights,

Regards,

Sylvain Brohée

[Paolo Di Tommaso]

Think the docs should explain the reason 

> When true the VM will NOT be provided with a public IP address, and only contain an internal IP. If this option is enabled, the associated job can only load docker images from Google Container Registry, and the job executable cannot use external services other than Google APIs (default: false). Requires version 20.03.0-edge or later

https://www.nextflow.io/docs/latest/google.html?highlight=useprivateaddress

--
You received this message because you are subscribed to the Google Groups "Nextflow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nextflow+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nextflow/2206fdf9-961d-4e29-cbd8-38938b29da46%40gmail.com.