Bug 1313218
| Summary: | Support proxies | ||
|---|---|---|---|
| Product: | Container Development Kit (CDK) | Reporter: | Eduardo Minguez <eminguez> |
| Component: | distribution | Assignee: | Lalatendu Mohanty <lmohanty> |
| Status: | MODIFIED --- | QA Contact: | Ondřej Pták <optak> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | unspecified | CC: | bgollahe, d.sastre.medina, erich, jgreguske, jkaur, kanderso, lmohanty, pep, rwagner, timoran, tkimura, veillard |
| Target Milestone: | beta4 | ||
| Target Release: | 2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Eduardo Minguez
2016-03-01 08:33:34 UTC
This seems very important for me, asking for blocker. Looking into: https://docs.docker.com/engine/admin/systemd/ It seems to me we would need to use both HTTP_PROXY and NO_PROXY settings and user friendly way would be either configuration via Vagrantfile or better via service-manager plugin. I guess we do not want instruct users to edit systemd files... Trello card for this, will go in next sprint: https://trello.com/c/6eX7wraX/185-proxy-support-in-cdk Daniel There are two patches/ pull requests in upstream for fixing the issue [1] [2]. [1] https://github.com/projectatomic/adb-utils/pull/150 [2] https://github.com/projectatomic/adb-vagrant-registration/pull/88 All the above PRs has been merged. However we are seeing one issue with libvirt provider [1]. But it seems it might be issue with the test setup and we are looking in to it. The fix should be available as part of CDK 2.2. [1] https://github.com/projectatomic/adb-utils/issues/159 We have released the vagrant-registration plugin with fix in upstream i.e. https://rubygems.org/gems/vagrant-registration/versions/1.2.3 |