From: Joe Doss <joe@solidadmin.com>
To: adam souzis <adam@souzis.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: trouble installing on Fedora and CentOS
Date: Wed, 9 Aug 2017 09:54:06 -0500 [thread overview]
Message-ID: <7ba12438-298e-7cad-af65-c39ccb0de07f@solidadmin.com> (raw)
In-Reply-To: <CAJkVDg1-0rQU0KCoVTyyiEK2Usuyf=djszSJ2KhP6xJdZwgzow@mail.gmail.com>
On 08/09/2017 07:39 AM, adam souzis wrote:
> Hi Joe,
>
> Thanks for looking into this, yes you are correct that my machine's
> kernel version didn't match with what the rpm expected, I discovered
> this when I tried to build from source. Maybe this error should be fatal
> or output a message suggesting the expected kernel?
I am not sure how must effort that will require. If anyone has any ideas
on how to make this edge case better I am all ears.
For the time being, just ensure you have the right kernel-headers
installed for your running kernel and you should be fine.
> Have you tried to get your packages to working on an Atomic Host build?
> When I did, the install failed:
>
> [fedora@atomic~]$ uname -r
>
> 4.11.11-300.fc26.x86_64
>
> [fedora@atomic~]$ sudo rpm-ostree install
> ./wireguard-dkms-0.0.20170726-1.fc26.noarch.rpm
>
> Checking out tree 0715ce8... done
>
> Resolving dependencies... done
>
> Overlaying... done
>
> *error: *Running %post for wireguard-dkms: Executing
> bwrap(/usr/wireguard-dkms.post): Child process exited with code 8
>
> So I just copied the wireguard.ko and wg binaries over from a regular
> Fedora 26, did an insmod and things are working, so I'm good for now.
If I get some time I will ask the folks in #atomic what the best method
is for adjusting a F26 RPM to work in Atomic. My hunch it is failing
when it tries to write the WireGuard files to /usr/src/ which is read
only (I think).
Joe
--
Joe Doss
joe@solidadmin.com
prev parent reply other threads:[~2017-08-09 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 19:58 adam souzis
2017-08-08 20:08 ` Bruno Wolff III
2017-08-08 22:49 ` adam souzis
2017-08-08 23:21 ` Jason A. Donenfeld
2017-08-09 1:51 ` Joe Doss
2017-08-09 12:39 ` adam souzis
2017-08-09 14:54 ` Joe Doss [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7ba12438-298e-7cad-af65-c39ccb0de07f@solidadmin.com \
--to=joe@solidadmin.com \
--cc=adam@souzis.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).