On 14 July 2016 at 16:56, Olaf Meeuwissen wrote:
> Thanks, but please note that the daemon uses *environment variables* to
> apply proxy settings. You cannot set those in daemon.json, AFAICS.
> You'd still need to use /etc/default/docker.io, the systemd drop-in
> approach or patch up the init scr
intrigeri writes:
> I'll let you handle that: I merely worked on this bug to give a hand
> and help a bit polish Jessie (and more specifically, the transition to
> systemd), but I don't suffer from it myself... so far.
I solved my "transition" to systemd with `apt-get purge systemd` ;-)
> Assum
On 7 March 2015 at 05:58, intrigeri wrote:
> a) Drop the EnvironmentFile= support, on the grounds that it's
> incomplete and misleading. Then document in README.Debian that
> under systemd:
> - /etc/default/docker is ignored (and maybe make that file point
> to README.Debian);
>
On 7 March 2015 at 07:44, Tianon Gravi wrote:
> I like (a), ...
I should add that (a) is also something I'd feel good about pushing
most of upstream, since their packages would benefit from noting this
difference too.
♥,
- Tianon
4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4
--
Hi,
Tianon Gravi wrote (04 Mar 2015 17:10:07 GMT) :
> This would definitely need to be proposed upstream (see "contrib/init"
> in the upstream repo),
I'll let you handle that: I merely worked on this bug to give a hand
and help a bit polish Jessie (and more specifically, the transition to
systemd
On 21 January 2015 at 01:47, intrigeri wrote:
> Apart of improving the comments, given we want to support both init
> systems in Debian, and to have a single "default" file configure both,
> it seems that we should remove the `export' from
> contrib/init/sysvinit-debian/docker.default, and have th
intrigeri writes:
> Hi,
>
> Olaf Meeuwissen wrote (31 Oct 2014 04:13:11 GMT) :
>> Actually, I take that partially back. It turns out to be dependent on
>> what init system you are using. For the traditional SysV init and
>> Upstart the `export` seems to be needed but for systemd it causes the
>
Hi,
Olaf Meeuwissen wrote (31 Oct 2014 04:13:11 GMT) :
> Actually, I take that partially back. It turns out to be dependent on
> what init system you are using. For the traditional SysV init and
> Upstart the `export` seems to be needed but for systemd it causes the
> variable to be ignored, as
Olaf Meeuwissen writes:
> What did solve my problem was dropping the `export` in the configuration
> file. So, I now have
>
> http_proxy="http://127.0.0.1:3128/";
>
> as my *only* proxy related setting in /etc/default/docker and searching
> the Docker Hub Registry works fine.
>
> Please drop `
Package: docker.io
Version: 1.3.0~dfsg1-1
Severity: normal
Dear Maintainer,
In order to search the Docker Hub Registry, I need to go through a
proxy. So I modified /etc/default/docker to have a
export http_proxy="http://127.0.0.1:3128/";
line and restarted the docker daemon. The same proxy
10 matches
Mail list logo
