unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Joshua Branson <jbranso@dismail.de>
To: "Sébastien Pierre" <sebastien.pierre@nzx.com>
Cc: help-guix@gnu.org
Subject: Re: Install and reinstall issues on Fedora 34
Date: Wed, 30 Jun 2021 11:39:08 -0400	[thread overview]
Message-ID: <87zgv7xsyr.fsf@dismail.de> (raw)
In-Reply-To: <CANBUJkyPfOH5Ri-nrWxCTcF3AL0UOwgSgUkej_SpiT3iQS2MUw@mail.gmail.com> ("Sébastien Pierre"'s message of "Thu, 17 Jun 2021 10:57:00 +1200")

Sébastien Pierre <sebastien.pierre@nzx.com> writes:

> Hi there,
>
> I am evaluating Guix and am running into some issues getting it to work
> under Fedora 34 Workstation. I followed the binary install instructions
> <https://guix.gnu.org/manual/en/html_node/Binary-Installation.html>,
> running the install script from an interactive root shell. All went well, I
> rebooted the VM, but then guix-daemon failed to start:

So is Fedora running on the VM?  And you are running guix the package
manager on top of Fedora, which is inside a vm?  What are you running on
metal?  What operating system is touching your hard drives?

Just check the basics...GNU Guix, the package manager, should run on any
distro.  Yes Fedora's SELinux policy could be breaking some things...

>
> × guix-daemon.service - Build daemon for GNU Guix
>      Loaded: loaded (/etc/systemd/system/guix-daemon.service; enabled;
> vendor preset: disabled)
>      Active: *failed *(Result: exit-code) since Tue 2021-06-15 08:50:44
> NZST; 2 days ago
>     Process: 691
> ExecStart=/var/guix/profiles/per-user/root/current-guix/bin/guix-daemon
> --build-users-group=guixbuild (code=exited, status=203/EXEC)
>
> Jun 15 08:50:44 fedora systemd[1]: Started Build daemon for GNU Guix.
> Jun 15 08:50:44 fedora systemd[691]: guix-daemon.service: *Failed to locate
> executable* /var/guix/profiles/per-user/root/current-guix/bin/guix-daemon:
> Permission den>
> Jun 15 08:50:44 fedora systemd[691]: guix-daemon.service: Failed at step
> EXEC spawning
> /var/guix/profiles/per-user/root/current-guix/bin/guix-daemon: Permission
> de>
> Jun 15 08:50:44 fedora systemd[1]: guix-daemon.service: Main process
> exited, code=exited, status=203/EXEC
> Jun 15 08:50:44 fedora systemd[1]: guix-daemon.service: Failed with result
> 'exit-code'.
>
> It seems like a permission error, as the ExecStart path exists and resolves
> to the /gnu/store, which is ther. Manually running the command does work as
> well. I did try to replace the readlink -f'ed path in the SystemD service:
>
> ExecStart=/gnu/store/0iii8i1lc4wg3wccs1db7y7d8lg80i04-guix-1.3.0/bin/guix-daemon
> --build-users-group=guixbuild
>
> But the same Permission Denied/Failed to locate issue remains. I know that
> Fedora uses SELinux which sometimes causes some problems, but I'm not sure
> about how to resolve that.
>
> Help would be appreciated :)
>
> Many thanks
>
> Sebastien

--
Joshua Branson (joshuaBPMan in #guix)
Sent from Emacs and Gnus
  https://gnucode.me
  https://video.hardlimit.com/accounts/joshua_branson/video-channels
  https://propernaming.org
  "You can have whatever you want, as long as you help
enough other people get what they want." - Zig Ziglar


  reply	other threads:[~2021-06-30 16:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-16 22:57 Install and reinstall issues on Fedora 34 Sébastien Pierre
2021-06-30 15:39 ` Joshua Branson [this message]
2021-06-30 21:01 ` Ricardo Wurmus

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zgv7xsyr.fsf@dismail.de \
    --to=jbranso@dismail.de \
    --cc=help-guix@gnu.org \
    --cc=sebastien.pierre@nzx.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 read-only IMAP folder(s) and NNTP newsgroup(s).