ignore proxies from the env vars when using UNIX Domain Sockets

[eighthave]

closes #390

[packit-as-a-service]

We were not able to find or create Copr project packit/containers-podman-py-391 specified in the config with the following error:

Cannot create a new Copr project (owner=packit project=containers-podman-py-391 chroots=['centos-stream-10-x86_64', 'centos-stream-9-x86_64']): Response is not in JSON format, there is probably a bug in the API code.

---

Please check your configuration for:

1. typos in owner and project name (groups need to be prefixed with @)
2. whether the project name doesn't contain not allowed characters (only letters, digits, underscores, dashes and dots must be used)
3. whether the project itself exists (Packit creates projects only in its own namespace)
4. whether Packit is allowed to build in your Copr project
5. whether your Copr project/group is not private

[eighthave]

Looks like the test failures are unrelated to my change.

[rhatdan]

LGTM
@umohnani8 @jwhonce PTAL

[jwhonce]

LGTM

@lsm5 Can you help with the centos issues?

@umohnani8 It appears podman-py/pull/374 introduced something that pylint=3.2.0 does not approve.

[inknos]

This PR looks good to me.

pull/374 introduced something that pylint=3.2.0 does not approve.

Looks like old_toml_file is not defined in all the if/else blocks

[umohnani8]

LGTM

[lsm5]

alright, packit failures are resolved.

[lsm5]

@umohnani8 @jwhonce @inknos unrelated, we should include rhel, centos and fedora testing for PRs with TMT like we do for some other projects.

• Would make unittest and make integration suffice, or do we need anything else?
• Do we also need to run podman-py reverse dependency tests on podman repo for every PR? (I think if these can always finish real fast and don't break often, it would be easier to pitch to podman)

[rhatdan]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eighthave, rhatdan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [rhatdan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment