Image quay.io/nebari/nebari-conda-store does not exist

[TheSenya]

I was trying to deploy nebari and I noticed that the image quay.io/nebari/nebari-conda-store did not exist in the quay.io registry. Has this image been removed, are there plans to put it back? In the mean time is there another publicly available image I can use to replace the nebari conda store.
If I got something wrong please let me know.

[viniciusdc]

Hey @TheSenya, greetings. We have not published the conda-store images to nebari registry yet, its been recently migrated to the conda-incubator, and there are other milestones that we are currently working on before migrating it.

Here's where nebari uses it,

nebari/src/_nebari/stages/kubernetes_services/template/modules/kubernetes/services/conda-store/variables.tf

Lines 37 to 41 in ff11b59

	variable "conda-store-image" {
	description = "Conda-Store image"
	type = string
	default = "quansight/conda-store-server"
	}

I am curious as to where that error might've came up from, could you share the error message if possible?

[TheSenya]

@viniciusdc thanks for the update. I was simply trying to perform a docker pull quay.io/nebari/nebari-conda-store and I gave me the error that the image does not exist (not actually using quay.io but instead a company proxy to quay.io).

What I'm trying to do is to deploy nebari first locally and then to AKS, but given the fact that I must pull ALL images from my companies proxied registry I've had to create a custom build script to manually deploy all terraform stage rather than using nebari. I'm not sure if this is 100% the right approach but what I've seen from the terraform stages there are multiple locations where the images are hardcoded and can not be overridden via the terrafrom_override configs for nebari (correct me if I'm wrong).

Also I've tried to add certificates to Kubernetes to allow it to pull directly from my specified registries but not dice on that

I'm pretty new to Kubernetes in general so I may not be going about things the right way, but where trying to use Nebari givens its really cool features. This may be a big ask but if you have time I would love to have a call with either you or someone from the nebari team to discuss all these factors.

Thanks!

[viniciusdc]

Hey @TheSenya, thanks for the reply. Indeed, right now Nebari does not support a custom OCI registry for the images used by its components. If you are willing to move all the images to your internal registry, then I would suggest using _overrides.tf files in each stage module/submodule so that you can change where the image is being pulled from.

Also I've tried to add certificates to Kubernetes to allow it to pull directly from my specified registries but no dice on that

Regarding this part, it should've worked... We internally use a tool called k9s to ease the inspection of Kubernetes resources: https://nebari.dev/docs/how-tos/debug-nebari#getting-started-with-k9s. I would try installing it and inspecting whether the registry manifest has been configured correctly, while also checking the pod events to see what error is coming from them when pulling the image. Usually, it says whether it is an unreachable error or a credentials issue.

For the meeting, you can join our community meetings. They happen every two weeks. We just had one today, so the next one will be on the 24th of March: https://nebari.dev/community/introduction#community-meetings