Danny Milosavljevic writes:
> Hi Allan,
>
> I've pushed a new way to get rid of this bug to guix master.
>
> Could you try
>
> guix pull
>
> and then
>
> guix reconfigure
>
> and report back?
Success! Thank you very much.
--
Allan Adair
http://allan.adair.io
odprobe", "overlay").Run()
>
> f, err := os.Open("/proc/filesystems")
> if err != nil {
> return err
> }
> defer f.Close()
>
> s := bufio.NewScanner(f)
> for s.Scan() {
> if s.Text() == "nodev\toverlay" {
> return nil
> }
> }
> logrus.WithField("storage-driver", "overlay2").Error("'overlay' not
> found as a supported filesystem on this host. Please ensure kernel is new
> enough and has overlay support loaded.")
> return graphdriver.ErrNotSupported
> }
>
> We don't load "overlay" explicitly. The above is some weird
> contraption--loading kernel modules from random user space programs.
> Seriously?
>
> And I suspect that modprobe is not found in your system profile.
>
> As a workaround, try adding "kmod" to the list of packages in your
> operating-system in your system configuration and reconfigure.
>
> But the real fix is for Docker to stop doing this weird thing in the first
> place. Nowadays, modules are autoloaded when someone is accessing the thing
> (by udev, or just by using it etc).
>
> In this case, they do
>
> if err := mount("overlay", mountTarget, "overlay", 0, mountData); err
> != nil {
>
> later on. And that's how it should have been detecting it, too.
--
Allan Adair
http://allan.adair.io
Hi Danny.
Danny Milosavljevic writes:
> Hi Allan,
>
> On Mon, 11 Mar 2019 09:59:19 +0100
> Allan Adair wrote:
>
>> Sorry for the late response. I was offline for the last week or so.
>
> No problem!
>
>>
>> I ended up having to repeat the first c
Hi Danny.
Sorry for the late response. I was offline for the last week or so.
I ended up having to repeat the first command with sudo
privileges. Please see below.
Danny Milosavljevic writes:
> Hi,
>
> On Fri, 01 Mar 2019 14:50:39 +0100
> Allan Adair wrote:
>
>&g
Björn Höfling writes:
> On Fri, 1 Mar 2019 14:09:32 +0100
> Andreas Enge wrote:
>
>> On Fri, Mar 01, 2019 at 09:58:20AM +0100, Allan Adair wrote:
>> > >> > I am however able to execute "sudo herd start
>> > >> > dockerd" after bootin
it will still not
>> > start.
>>
>> I can confirm this behaviour, though I haven't yet investigated it
>> further.
>
> Could this be yet another manifestation of
>https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34580 ?
> Services not started on boot?
>
> Andreas
I'm not so sure. One thing that I am unable to do is "herd start
dockerd".
--
Allan Adair
http://allan.adair.io
e I have included dockerd in my user
profile. I can also "guix system reconfigure" at this point to start
the dockerd service, but then at the next boot it will still not start.
Danny Milosavljevic writes:
> Hi Allan,
>
> On Tue, 12 Feb 2019 09:05:10 +
> A
On 2019-02-11 17:31, Danny Milosavljevic wrote:
Hi Allan,
I've added some more requirements--let's see.
Can you guix pull and guix reconfigure and then try again once more?
Still no luck. Do you face the same issue?
--
Allan Adair
+47 468 12 135
al...@adair.io
http://allan.adair.io
host networking is set up.
I've added it--let's see.
Allan, can you guix pull and guix reconfigure and then try again?
I guix pulled and guix system reconfigured. After a successful
reconfigure and reboot, the service was still not started.
--
Allan Adair
+47 468 12 135
al..
