Community
Chat Logs
Thursday, October 15, 2026 (America/New_York)
- phalethI've moved haproxy and dataplane api to a podman container named 000001-repopack-site-haproxy
- bluehi phaleth
- bluewas that necessary?
- phalethyeah, it's easier for repopack to take control over deployment
- blueah ok
- phalethshould do the same with buildkit next, after that prometheus and grafana
- phalethideally only podman and VPN should be installed directly on the OS
- bluebtw repopack is now at reliably <300mb
- bluebut I'm still profiling it
- phalethgreat :)
- phaleththat's a huge achievement, how did that happen?
- phalethrepopack runtime is up only for 3 hours now
- phalethfor VPN I started looking into wireguard, cause it's simple and there are also containers, so in the end it may not end up on host, but not sure
- phalethI mean the container can be on host network and then that should be the same, it's just wireguard will be in a container
- bluewell I've been profiling and improving stuff in repopack itself mostly
- bluewe'll see. I redeploy quite often so that could be masking it
- bluebut it reliably stays under 400mb now
- phalethok, but do you know what was leaking memory?
- phalethyeah
- bluehttps://repopack.com/project/repopack/tasks/500
- blueseems like SSE was partly to blame
- bluethis is still being followed-up
- bluehttps://repopack.com/project/repopack/tasks/544?tasks=status%3Dopen
- blueI'm not done yet with profiling and optimising
- bluebut at the present moment, I think we can safely say primate isn't leaking any memmory
- bluememory*
- blueand never has, in fact
- phalethoh, clanker can do this kinda peeking into the process
- phalethyeah, I just call it leaking memory, but you know some kind of stale cache that never clears