night lynx
Doing a Harvest POC deployment ahead of some ASAr2 boxes landing... reviewing https://netapp.github.io/harvest/25.08/install/podman/
Any one have any experience (or knowing of any issues) with using more current versions?
Podman 4.9.4
Docker Compose 2.40.2
RHEL 8.10
I'm kinda green in this space and it's been requested that I look at Podman vs Docker
long ruin
hi @night lynx podman should work well with Harvest on RHEL. If you go that route, checkout quadlet's too. They're pretty cool if you like strong systemd integration https://netapp.github.io/harvest/25.08/install/quadlet/
night lynx
Was on my list after getting through the basics 😁
Was just curious on versioning since the doc called out some older ones
long ruin
newer versions worked fine when I put the quadlet documentation together in Jan
night lynx
running the container as root hasn't been a problem... but I'm not getting very far on following the steps as a non-root user
`harvest@harvestdev01:(RC=0):/home/harvest/container
10:50:45 # systemctl --user enable podman.socket
Failed to connect to bus: No such file or directory
harvest@harvestdev01:(RC=0):/home/harvest/container
10:51:47 # podman info | grep runRoot
runRoot: /tmp/containers-user-1112/containers
harvest@harvestdev01:(RC=0):/home/harvest/container
10:51:49 # sudo curl -H "Content-Type: application/json" --unix-socket /var/run/docker.sock http://localhost/_ping
OK`
went down some rabbit holes on 'loginctl enable-linger [username]' but no changes
the harvest generate is using a difference uid:gid than I'd expect:
`harvest@harvestdev01:(RC=0):/home/harvest/container
10:56:07 # HYML="/home/harvest/harvest.yml"; docker run --rm --env UID=$(id -u) --env GID=$(id -g) --entrypoint "bin/harvest" --volume "$(pwd):/opt/temp" --volume "${HYML}:${HYML}" ghcr.io/netapp/harvest:latest generate docker full --output harvest-compose.yml --config "${HYML}"
Wrote file_sd targets to container/prometheus/harvest_targets.yml
Start containers with:
docker compose -f prom-stack.yml -f harvest-compose.yml up -d --remove-orphans
harvest@harvestdev01:(RC=0):/home/harvest/container
10:56:18 # ll
total 8
drwxr-x---. 2 494327 494327 6 Oct 31 10:56 cert
drwxr-x---. 13 494327 494327 166 Oct 31 10:56 conf
drwxr-xr-x. 3 494327 494327 24 Oct 31 10:56 container
drwxr-xr-x. 4 494327 494327 43 Oct 31 10:56 grafana
-rw-------. 1 494327 494327 398 Oct 31 10:56 harvest-compose.yml
-rw-------. 1 494327 494327 1595 Oct 31 10:56 prom-stack.yml`
I can recursively chown them, but then the failures to connect to unix:///tmp/containers-user-1112/containers
long ruin
well, phooey. Just going off web searches here, but what if you try running loginctl show-user $USER
night lynx
ah, yea, I should have posted that too... that was another odd one, I am logged as the harvest user yet it still says:
`harvest@harvestdev01:(RC=1):/home/harvest
12:32:17 # whoami
harvest
harvest@harvestdev01:(RC=0):/home/harvest
12:32:50 # loginctl show-user $USER
Failed to get user: User ID 1112 is not logged in or lingering
harvest@harvestdev01:(RC=1):/home/harvest
12:32:56 # loginctl show-user harvest
Failed to get user: User ID 1112 is not logged in or lingering`
long ruin
strange. I don't see errors like that on any systems I try. I would have suggested trying sudo loginctl enable-linger harvest but sounds like you have already down that
night lynx
yea, ran that one down too... and I see in it /var/lib/systemd/linger:
`harvest@harvestdev01:(RC=0):/home/harvest
12:47:15 # sudo loginctl enable-linger harvest
harvest@harvestdev01:(RC=1):/home/harvest
12:47:28 # ll /var/lib/systemd/linger/
total 0
-rw-r--r--. 1 root root 0 Oct 31 12:47 harvest`
long ruin
but even after that you still see this command fail, right? loginctl show-user harvest
night lynx
yep
`harvest@harvestdev01:(RC=0):/home/harvest
12:47:38 # loginctl show-user harvest
Failed to get user: User ID 1112 is not logged in or lingering
harvest@harvestdev01:(RC=1):/home/harvest
12:51:21 # sudo loginctl show-user harvest
Failed to get user: User ID 1112 is not logged in or lingering`
long ruin
strange. you might need to find a RHEL expert to ask
night lynx
so yea, definitley something goofy going on with the loginctl / logind ... my RHEL SMEs were stumped ... we're re-imaging the box instead of banging out heads against the wall