Talk:Docker: Difference between revisions

From Alpine Linux
(useful info but commented-out?)
 
m (Unsigned comment attribution.)
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
The sourcecode of this page has some commented-out information, which would actually be useful to include - I encountered problems with docker which would have been resolved by this commented-out information.  Is there a reason not to include it?  See below:
== Runlevel ==


you'll need to disable some kernel security flags:
In this page, it's noted that Docker should be started at runlevel "boot", but it seems to contradict the rules described in this page: [[Alpine_Linux_Init_System|Alpine Linux Init System]]. Is this a mistake, or is there a valid reason why Docker should be started early?
'''
sysctl -w kernel.grsecurity.chroot_caps=0
sysctl -w kernel.grsecurity.chroot_deny_chmod=0
sysctl -w kernel.grsecurity.chroot_deny_chroot=0
sysctl -w kernel.grsecurity.chroot_deny_mknod=0
sysctl -w kernel.grsecurity.chroot_deny_mount=0
'''


Without the '''sysctl -w kernel.grsecurity.chroot_deny_chmod=0''', I had error: '''Error pulling image (jessie) from docker.io/library/debian, ApplyLayer exit status 1 stdout: stderr: chmod /bin/mount: permission denied'''
<small><span class="autosigned">—&nbsp;Preceding [[Help:Signature|unsigned]] comment added by [[User:Sprat|Sprat]] ([[User talk:Sprat|{{int:talkpagelinktext}}]] • [[Special:Contributions/Sprat|{{int:contribslink}}]]) 12:38, 10 May 2021‎</span></small>
 
-- KarlMW
 
----

Latest revision as of 02:54, 14 August 2023

Runlevel

In this page, it's noted that Docker should be started at runlevel "boot", but it seems to contradict the rules described in this page: Alpine Linux Init System. Is this a mistake, or is there a valid reason why Docker should be started early?

— Preceding unsigned comment added by Sprat (talkcontribs) 12:38, 10 May 2021‎