Awesome, thank you!
Paul
On Fri, Apr 3, 2015 at 5:18 PM, Gomex wrote:
> On 03-04-2015 17:45, Paul R. Tagliamonte wrote:
>> I'd prefer that we break if the docker group is on the system.
>>
>> If we do want to allow users to say ok, we'll use debconf. Don't use
>> echo and read. I won't apply th
On 03-04-2015 17:45, Paul R. Tagliamonte wrote:
> I'd prefer that we break if the docker group is on the system.
>
> If we do want to allow users to say ok, we'll use debconf. Don't use
> echo and read. I won't apply this. This is completely broken on
> graphical installers of debs.
>
> Thanks,
>
I'd prefer that we break if the docker group is on the system.
If we do want to allow users to say ok, we'll use debconf. Don't use
echo and read. I won't apply this. This is completely broken on
graphical installers of debs.
Thanks,
Paul
On Fri, Apr 3, 2015 at 4:43 PM, Gomex wrote:
> On 20-0
On 20-01-2015 13:49, go...@riseup.net wrote:
> On 2015-01-19 14:49, Tianon Gravi wrote:
>> On 19 January 2015 at 10:33, wrote:
>>> This can happen, but I can't see any possibility of a group docker
>>> causes
>>> any security problem.
>>
>> You probably want to give
>> https://docs.docker.com/art
Nice try Gomex! :-)
There is a good help to understand and use debconf:
http://www.fifi.org/doc/debconf-doc/tutorial.html
Other useful information:
https://en.wikipedia.org/wiki/Debconf_%28software_package%29#External_links
♥,
Aurium
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists
On 2015-01-19 14:49, Tianon Gravi wrote:
On 19 January 2015 at 10:33, wrote:
This can happen, but I can't see any possibility of a group docker
causes
any security problem.
You probably want to give
https://docs.docker.com/articles/security/#docker-daemon-attack-surface
a read-through. :)
On 2015-01-19 14:49, Tianon Gravi wrote:
On 19 January 2015 at 10:33, wrote:
This can happen, but I can't see any possibility of a group docker
causes
any security problem.
You probably want to give
https://docs.docker.com/articles/security/#docker-daemon-attack-surface
a read-through. :)
On 19 January 2015 at 10:33, wrote:
> This can happen, but I can't see any possibility of a group docker causes
> any security problem.
You probably want to give
https://docs.docker.com/articles/security/#docker-daemon-attack-surface
a read-through. :)
♥,
- Tianon
4096R / B42F 6819 007F 00F8
On 2015-01-19 13:51, Paul Tagliamonte wrote:
On Sun, Jan 18, 2015 at 09:19:19PM -0300, go...@riseup.net wrote:
Package: docker.io
Version: 1.3.3~dfsg1-2
When you have a external docker group (ex. LDAP group) with same name,
the
installation crashs. The shared group in external LDAP Server is a
On 19 January 2015 at 09:51, Paul Tagliamonte wrote:
> While true, I'm concerned about existing groups *unrelated* to docker
> being on the system already, giving rights to the group members when
> that's otherwise a bad idea.
I think it's also worth noting that Docker only reads /etc/group for
"
On Sun, Jan 18, 2015 at 09:19:19PM -0300, go...@riseup.net wrote:
> Package: docker.io
> Version: 1.3.3~dfsg1-2
>
> When you have a external docker group (ex. LDAP group) with same name, the
> installation crashs. The shared group in external LDAP Server is a best
> pratice.
While true, I'm conce
Package: docker.io
Version: 1.3.3~dfsg1-2
When you have a external docker group (ex. LDAP group) with same name,
the installation crashs. The shared group in external LDAP Server is a
best pratice.
Follow the patch to fix this possible problem in DEBIAN/postinst file:
6c6
12 matches
Mail list logo
