Best posts made by felfert

Hi,

Just noticed after update to proget (docker) 25.0.8:

In the gui, the version of a rpm package is displayed correctly:

But dnf (or yum) cannot find the package anymore. sudo dnf update should update the locally installed cloudtools, but instead the following is displayed:

Notice the release number in the listing is cut off (dash remains) and when the actual download is attempted, both the dash and the number are missing.

Suspect: PG-3074 (just a gut feeling )

Cheers,
-Fritz

As a reference and perhaps an example for how to run proget as quadlets, here are my config files for quadlets:

1. /etc/containers/systemd/mssql.container

[Unit]
Description=Microsoft SQL server

[Service]
Restart=always
# Extend Timeout to allow time to pull the image
TimeoutStartSec=900

[Container]
Image=mcr.microsoft.com/mssql/server:2019-latest
EnvironmentFile=/etc/mssql.env
Volume=/var/data/mssql:/var/opt/mssql:U,Z
Network=inedo.network
HostName=inedo-sql

[Install]
WantedBy=multi-user.target

2. /etc/containers/systemd/proget.container

[Unit]
Description=Inedo proget
After=mssql.service
Requires=mssql.service

[Service]
Restart=always
# Extend Timeout to allow time to pull the image
TimeoutStartSec=900

[Container]
Image=localhost/proget:current
EnvironmentFile=/etc/proget.env
Volume=/var/data/proget/backups:/var/proget/backups:z
Volume=/var/data/proget/database:/var/proget/database:z
Volume=/var/data/proget/extensions:/var/proget/extensions:z
Volume=/var/data/proget/packages:/var/proget/packages:z
Volume=/var/data/proget/ssl:/var/proget/ssl:z
Volume=/etc/localtime:/etc/localtime:ro
Network=inedo.network
PublishPort=80:80
HostName=proget

[Install]
WantedBy=multi-user.target

3. /etc/containers/systemd/inedo.network

[Network]

Remarks:

The Image in /etc/containers/systemd/proget.container is intentionally referencing a locally tagged image. This goes together with the following script for easily updating
proget:

#!/bin/bash
set -e
set -x
systemctl stop proget
sleep 5
itag=latest
if [ $# -eq 1 ] ; then
    itag=$1
fi
podman tag proget:current proget:previous
podman pull proget.inedo.com/productimages/inedo/proget:${itag}
podman tag proget.inedo.com/productimages/inedo/proget:${itag} proget:current
systemctl start proget
cat<<EOF
Upgrade finished and proget started.
Old image has benn tagged proget:previous
EOF

and: Obviously, the hierarchy below /var/data/proget has to be manually created in advance. /var/data/proget is on a separate virtual disk.

Forgot the env files referenced in the .container files:

/etc/mssql.env:

ACCEPT_EULA=Y
MSSQL_SA_PASSWORD=*****REDACTED*****
MSSQL_PID=Express

/etc/proget.env:

PROGET_SQL_CONNECTION_STRING=Data Source=inedo-sql; Initial Catalog=ProGet; User ID=sa; Password=*****REDACTED*****
TZ=Europe/Berlin

Both are mode 0600, so that the passwords in there are a little bit more protected.

And: Just after freshly setting it all up, I normally immediately migrate to embedded postgres and then remove the mssql container as well as the inedo network.

Cheers
-Fritz

@wechselberg-nisboerge_3629 said in ERROR while migrating maven repository from Jfrog Artifactory.:

I am especially confused about the fact that it prints Windows paths, even though it is running as Linux Docker container.

That one fooled me previously as well, but if you look carefully, those are source paths from their build-system
e.g. C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\...

@atripp I tested this one and it works.

However:
In the meantime, i have updated to the released 25.0.9 (aka latest) and now I cannot reproduce the error either - even if I explicitely revert the function to the old one where it produced the error before

So I'm afraid that i might not be a reliable tester for this specific error anymore.

Cheers
-Fritz