PyOCI – Publish and install private Python packages using OCI/Docker registries
1–10 of 15 posts
Re: PyOCI – Publish and install private Python packages using OCI/Docker registries
#2Or you could use GitLab which has support for Python packages without a proxy.
Re: PyOCI – Publish and install private Python packages using OCI/Docker registries
#3can we agree to use OCI for everything :D
Re: PyOCI – Publish and install private Python packages using OCI/Docker registries
#4can we agree to use OCI for everything :D
as long as we can convert the OCI to an bootable VM image, i am fine with that. But i also think, there's an size limit
Re: PyOCI – Publish and install private Python packages using OCI/Docker registries
#5can we agree to use OCI for everything :D
as long as we can convert the OCI to an bootable VM image, i am fine with that. But i also think, there's an size limit
There are still growing pains, but https://github.com/osbuild/bootc-image-builder exists and is likely to become exactly that in the general case (as it already is for the redhat family).
Re: PyOCI – Publish and install private Python packages using OCI/Docker registries
#6Would be nice to see at least a high-level overview of how it works under the hood. Is it doing anything interesting with reusable layers? Actually, thinking further that might be a moot point; I feel like running as a remote proxy loses some fun optimization chances. I could imagine a world where you install a package from the host's pip/uv, and then add it to a container image, and both of those are actually the same thing on disk. (Granted, that's likely harder to implement)
Re: PyOCI – Publish and install private Python packages using OCI/Docker registries
#7can we agree to use OCI for everything :D
as long as we can convert the OCI to an bootable VM image, i am fine with that. But i also think, there's an size limit
Oh those size limits are pushed plenty by AI images, no worries. I recently had a good laugh when I found a docker image that was 2 - 3 times as big as the OS partition of a lot of our smaller servers.
And our OS image build order would reuse layers better than those.
Re: PyOCI – Publish and install private Python packages using OCI/Docker registries
#8Re: PyOCI – Publish and install private Python packages using OCI/Docker registries
#9Re: PyOCI – Publish and install private Python packages using OCI/Docker registries
#10Earlier quoted context omitted.
as long as we can convert the OCI to an bootable VM image, i am fine with that. But i also think, there's an size limit
Oh those size limits are pushed plenty by AI images, no worries. I recently had a good laugh when I found a docker image that was 2 - 3 times as big as the OS partition of a lot of our smaller servers. And our OS image build order would reuse layers better than those.
No doubt, I've regularly encountered ~2TB container images with enough layers to make one weep. SISO, slop in/slop out (sorry).