Hello everyone - I’ve been working through the various demos for Jetson Orin Nano Super Dev Kit. I have run into an issue with accessing : https://pypi.jetson-ai-lab.dev/jp6/cu126 When running commands inside the nanoowl container, such as “pip install aiohttp” it seems that the index has been unreachable for at least the last 72 hours. This fails inside Docker container or on the Jetson Nano itself. Can anyone advise if this is a known outage or issue?
Looking in indexes: https://pypi.jetson-ai-lab.dev/jp6/cu126
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘NewConnectionError(’<pip._vendor.urllib3.connection.HTTPSConnection object at 0xffffb2e8ff40>: Failed to establish a new connection: [Errno 113] No route to host’)': /jp6/cu126/pip/
pypi.jetson-ai-lab.dev is down. We are improving security and performance. Meanwhile please use pypi.jetson-ai-lab.io by setting the enviroment variable INDEX_HOST=jetson-ai-lab.io in .env file.
The repo owner has stepped down, but we try to keep most of the resources available to minimize the impact.
The URL has been changed to https://pypi.jetson-ai-lab.io/.
You can follow the update on jetson-container to get the latest info:
The package is in the multiarch but there is no multiarch support in https://pypi.jetson-ai-lab.io.
Only Jetpack 6.2 (CUDA 12.6) and JetPack 7 (CUDA 13.x) are supported now.
But the Video Codec source file (.zip) can be found on the website directly:
So once I downloaded the video codec from that site, how would make the jetson-containers build process use that downloaded version instead of where it’s currently trying to get it (https://apt.jetson-ai-lab.io/multiarch)?
FWIW: I ended up downloading the Video Codec SDK .zip file and placed it in jetson-containers/packages/multimedia/video-code-sdk. I also modified install.sh in that folder so that variable “ZIP” pointed to the downloaded file (“./Video_Codec_SDK_13.0.0.19.zip”) and commented out the wget code that was trying to download it.
Both .io and .dev are down for me. Was this a single point of failure? One person and one person only in controller of all of jetson py package distribution?