-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to use proxy server with rpm-ostree #762
Comments
rpm-ostree uses https://github.com/rpm-software-management/libdnf/ which handles proxy configuration via the same mechanisms as the original Note that for the libostree side (base tree/image) updates, you'll need to edit a different file; see #208 |
@cgwalters I haven't yet tried it to edit yum. For the record I have Centos Atomic Host running. Don't know if that matters. |
@cgwalters in #208 (comment) is a little bit explained about the problem, unfortunately it doesn't make it clear (for me) where and how? |
Reference: projectatomic/atomic-site#428 |
@rgruyters To clarify, for proxy settings affecting For proxy settings affecting |
@jlebon thanks for clearing this. Although I have checked but I didn't found a |
Right, rpm-ostree uses libdnf which currently does not have a global configuration file, only per-repository. |
Oh right, sorry for the confusion there. I amended the comment for posterity. |
Really guys? Do we now have to edit proxys everywhere…?! I work in different environments and thus already have to replace my proxy file in |
Found this snippet in #208:
This seems to work for |
rpm-ostree should read all_proxy, http_proxy and https_proxy variables like dnf and yum. |
saved my live! Unfortunately rpm-ostree on FCOS32 ignored all my attempts using env vars. So at least from that point it must somehow differ from dnf/yum as those take env vars into account... |
In case it helps anyone else, for the workaround I had to set |
This worked for someone in https://discussion.fedoraproject.org/t/rpm-ostree-upgrade-and-proxy-server-timeout-was-reached/87051/10. Maybe we should document that as a workaround in the meantime? |
Unfortunately ostreedev/ostree-rs-ext#582 means this no longer works for OCI layers - perhaps it's time for dedicated proxy configuration in |
** Host system details **
Centos Atomic Host as VM
Provide the output of
rpm-ostree status
.** Expected vs actual behavior **
Expected:
Steps to reproduce it
Just run above command in a closed environment
Would you like to work on the issue?
Please let us know if you can work on it or the issue should be assigned to
someone else.
The text was updated successfully, but these errors were encountered: