Running Alpine in a Docker Container: Difference between revisions
No edit summary |
|||
(3 intermediate revisions by the same user not shown) | |||
Line 5: | Line 5: | ||
By default mkinitfs will use the running kernel to build the initfs. Since your Docker container is under some other kernel you need to specify this manually. | By default mkinitfs will use the running kernel to build the initfs. Since your Docker container is under some other kernel you need to specify this manually. | ||
<code>apk add linux-vanilla</code> | |||
<code>cat /usr/share/kernel/vanilla/kernel.release</code> | |||
<code>mkinitfs 4.19.41-0-vanilla</code> | |||
<code>mkinitfs `cat /usr/share/kernel/vanilla/kernel.release`</code> | |||
== See also == | == See also == |
Revision as of 17:38, 12 June 2019
Some things you might want to know if you're running Alpine in a Docker container.
using mkinitfs
By default mkinitfs will use the running kernel to build the initfs. Since your Docker container is under some other kernel you need to specify this manually.
apk add linux-vanilla
cat /usr/share/kernel/vanilla/kernel.release
mkinitfs 4.19.41-0-vanilla
mkinitfs `cat /usr/share/kernel/vanilla/kernel.release`