How can I tell Quarkus to not download images from quay.io, but from our local registry? We have configured our Nexus to be a cache/proxy for all images, since we also want to control what images are being used.
Related
in Google cloud Artifact Registry I ve created registry setup using maven type and remote functionality that supposed to mirror central.
It just doesn't work. My local test project is not able to fetch anything from such registry - I assume it should populate gcp registry cache from maven central and propagate any artifacts to my local .m2 directory.
In GCP web console remote type is marked as private preview - which is not really explained what it really means. I can definitely access this config, so I assume it should work :/
any ideas?
This is already mentioned in the public document that, GCP remote Artifact Registry is not Generally available for all customers.
Feature availability: This feature is only available to users who signed up for Artifact Registry private preview. For more information, contact your Google representative.
And the term Private Preview means features are ready for testing by customers and have limited support. But, they are not complete yet.
Have a look at this document for details about launching stages
My company uses WDS to deploy a variety of images to computers daily and today the boot image that pointed to all of the install images stored in WDS got overwritten. Now we're not able to access any of these and I've mostly been working with MDT so I'm not sure how to fix this. How do I set up a boot image pointing to the images we already have so we can start deploying these again?
In our company we have a data store that holds a wide variety of objects. This data store could be seen as a remote repository with a proprietary format. We would to make those objects available in a Nexus Repository Manager in a similar fashion as a remote Maven repository.
I wonder, would it be possible to create a proxy to this non-standard proprietary repository? Our proprietary data store has some version information, that we could map to a standard repository format.
Any help like an example or pointing me to documentation or existing plugins would be greatly appreciated.
You can proxy almost anything available via http(s) using a raw format proxy in nexus. Now if you want to proxy something that is not maven to a maven format, it's not possible.
If you have some version info you can use, I imagine you can create a script that would get a set of artifacts from your company repo and register them correctly using the nexus API in a maven hosted repo. That would not be a proxy but a partial async mirror.
I am trying to export assets out of Sonatype Nexus3 so that I can refactor our software artifact persistence. Primarily I want to use Nexus3 as a mirror/grouping tool for disparate repositories and not push to it directly as we currently do. For this to work I need to extract all of our Docker, Maven, and NPM components/assets out of it. The problem is, Nexus3 uses blob stores for asset persistence and I want the raw assets out.
Docker images are easy. I can just walk each repository's Docker Registry API to get a list of images to pull and then push them to a new location.
For Maven artifacts, however (and I assume this applies to NPM artifacts as well), I am unable to export repositories using something like the Maven Wagon Plugin's copy goal or just about anything else because all solutions that I have seen rely on directory listing which has not been implemented in Nexus3.
If I was able to get a listing of all components and associated assets in the Nexus3 hosted repositories this would be tedious but good enough to script. Is there some CLI or API trick to extracting such info out of Nexus3? Is there a query I can run against the embedded OrientDB instance after logging into the Karaf OSGi console?
Looking for some pointers!
You might find some help in the answer here: Using the Nexus3 API how do I get a list of artifacts in a repository
I think this will get you where you need to be :)
For running docker build of my Java application I need sensitive information (a password to access the nexus maven repository).
What is the best way to make it available to the docker build process?
I thought about adding the ~/.m2/settings.xml to the container but it lies outside of the current directory/context and ADD is not able to access it.
UPDATE: in my current setup I need the credentials to run the build and create the image, not when running the container later based on the created image
You probably want to look into mounting a volume from HOST into the container