CrazyMax

@stickz I planned to cut a release with your patches. I was thinking of this kind of semantic for versioning: `4.2.9-0.9.8+1-0.13.8+1-r0` `+` marks changes for patches so we can track...

https://github.com/crazy-max/docker-rtorrent-rutorrent/releases/tag/4.2.9-0.9.8_1-0.13.8_1-r0

> I suppose all torrents were parsed and tried to be announced to the trackers but timed out. Maybe rate-limit?

I think it's fine as we are just reading from this path. Can you update PIDs in https://github.com/crazy-max/docker-rtorrent-rutorrent/blob/1398e24d58f7c1c6928a2e2e2ecea1c3778f9a35/test/rtorrent-rutorrent.env#L2-L3 to smth like `1010` to make sure we can still read files?

Healthcheck ports are for internal use only. What's your use case?

> This is what is in my .rtorrent.rc This is your full `.rtorrent.rc` file content? Any logs?

> Why is yarn itself committed to the repository? We don't even store the modules we use in the repo. Yarn Modern (v2/v3) has some breaking changes with old v1...

@tonistiigi Setting yarn version in the Dockerfile works: https://github.com/docker/bake-action/compare/master...crazy-max:docker-bake-action:yarn-update-2#diff-3ed65642ec1610de6b0f162c77dc8499662ebeb7057d3f6c89108952d1cb33deR10-R14 but Dependabot will still use Yarn v1 and corrupt the lock file :disappointed:. Unfortunately we can't define yarn version in the...

@tonistiigi Switching back to npm looks to be the only alternative we have if you still don't want yarn installed within the repo: * https://github.com/docker/bake-action/pull/102

@tonistiigi Now using corepack to avoid having yarn in the repo.