Pinned Package Dependencies¶
A message similar to one of the following appears in an order run log to alert you:
[NodeThread:gpc] AC: 2020-05-08 18:03:04,563 INFO :
Installing runtime pip dependencies ...
[NodeThread:gpc] AC: 2020-05-08 18:03:12,068 ERROR : Unable to install dependencies, error:
[NodeThread:gpc] Collecting cryptography==2.4 (from -r runtime-requirements.txt (line 1))
[NodeThread:gpc] subprocess.CalledProcessError: Command '['pip3', 'install', '-r', 'runtime-requirements.txt']'
returned non-zero exit status 1.
[NodeThread:gpc] NodeConsumer:Run: run notebook fail: gpc
[VariationThread] Got an error in node gpc, stopping
Details¶
To specify specific package versions or to install newer versions to overwrite the
default Python packages,
you can set pinned (i.e. fixed) packages in a General Purpose Container (GPC) container node
config.json file as "dependencies".
Potential causes¶
Assigning pinned versions may cause dependency discrepancies.
Be mindful to not install a dependency that conflicts with any of the pre-installed tools.
Solution¶
Open the File Editor and verify the package versions used in the GPC. Update the versions as needed to remove conflicts.
When using a pinned version, it's best practice to set up a schedule to verify and update nodes.
Related topics¶
Note
Still not working? Contact DataKitchen Support. We can work through this together.