@atripp hi,
i already searched the internet and found nothing helpful. this is why i turned to you .
as said, i will start over and try to give you the output.
thanks,
udi
@atripp hi,
i already searched the internet and found nothing helpful. this is why i turned to you .
as said, i will start over and try to give you the output.
thanks,
udi
@atripp hi,
will take some time. just to be clear, i had one installation that worked but i wasn't the 1 who installed it i do not know what he did before.
i am starting a from scratch and again, the only permitted network connection to the outside is through the proget server. dns, ntp all is through the local network.
can you simulate my configuration at your network ?
maybe i must allow an initial connection to ubuntu for downloading gpg keys or something like that.
thanks,
udi
@atripp hi,
do you want me to start from the beginning ?
just to let you know that i have upgraded proget to the latest version.
Hi @atripp ,
@ time of writing this post i used the 1 version before the last stable release and today i have noticed that another release was published so i will upgrade to it.
i have followed the given instructions before posting this and i have to say that the same version of ubuntu desktop worked. after reinstalling and connecting the OS only to proget, i can't seem to update the apt and i am always stuck at "InRelease".
thank you very much
Hello,
i have installed ubuntu desktop 24.04.1 on a virtual machine with no internet connection.
dns is allowed and i have configured the apt source to go to the proget server.
proget is connected to the internet and offer http and https and is working.
when i run apt update i get errors about InRelease and it does not update. i have tried importing the feed's gpg key but i am getting an error the proget's generated gpg key is an unsupported filetype and that i do not have the public key.
i have configured the source list of the proget to use the http with [trusted=yes] and i can't still update apt i do not see the package i want. searching proget for the package and i can see it is there and should be compatible to this version of ubuntu. btw, my connector is configured to archive.ubuntu.com
help is appreciated.
Hi @atripp ,
found this config. i remember seeing it and left it checked because the description recommended it for registries like microsoft and for some reason i didn't pay attention to this until i figured out that i need to add "library" prefix.
thank you very much for all the help.
Hi @atripp ,
i have managed to successfully pull an image to proget.
the syntax i used is like: "podman pull xxx:8625/docker/library/ubuntu"
and this i discovered from the podman's response. when i tried looking up the additional "library" in the client setup of the feed or the documentation, i didn't find any thing related to that.
i have tried replacing "library" with something else like "udi" and it didn't work.
i then, tried to download fluent/fluent-id with the syntax "podman pull xxx:8625/docker/library/fluent/fluent-id" and it didn't work. i then deleted the "library" part and it worked.
is this how it is suppose to work ?
images without a prefix will need the "library" prefix ?
thanks
Hi @atripp ,
i have successfully updated to the latest version 2024.19 and get the same error.
i have created a lab in another computer connected directly to the internet (no proxy because i thought that maybe it is blocking something that i can't see) and got the same result. in the lab i used oracle linux 9.4 with podman instead of docker. upon pulling an image directly from docker, the image and the manifest are downloaded correctly.
just to make sure it is possible, i can configure a docker feed and pair up to it docker connectors and it should pull images as proxy like other feeds such as npm, is it ?
thanks
@atripp thank you very much.
will try the update.
thanks
Hello,
i am using proget free v2023.
i have created a container feed and attached him to docker hub connectors according to the urls in docker documentation. the connectors are healthy.
the feed allows anonymous pulling and i have con figured the feed in docker as insecure registry.
when i try pulling an image i always get manifest unknown error with\without doing docker login.
i use a proxy to connect to the internet and i do not see any problem there. other feeds like npm works fine.
10x