unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: jimmy@thrasibule.mx
Cc: help-guix <help-guix@gnu.org>
Subject: Re: guix pull: error: getting status of /var/guix/gcroots
Date: Thu, 6 Feb 2020 15:02:40 +0100	[thread overview]
Message-ID: <CAJ3okZ3YJt8AuN=JF-fqPcPZMeXJ+2hLWAqr4avUR+RLJUrc2Q@mail.gmail.com> (raw)
In-Reply-To: <CAMqSRmC2ksHPjsLgSwNDXKN=QzoB4dq3+QnT_ji1EHom2z9nUw@mail.gmail.com>

Hi,

On Thu, 30 Jan 2020 at 14:11, Jimmy Thrasibule
<jimmy.thrasibule@gmail.com> wrote:

> I'm building a Docker image in order to get a GuixSD by using the ``guix
> system docker-image`` command. See the Dokerfile at:
> https://bitbucket.org/x237net/guixsd/src/master/src/Dockerfile.

Instead, the issue should come from this file:

https://bitbucket.org/x237net/alpine-guix/src/master/src/Dockerfile


>     guix pull: error: getting status of /var/guix/gcroots: Operation not
> permitted

I do not have carefully look to your files, but the issue should be:
 - wrong permission
 - /var/guix is not exposed



> Again, I successfully built the image on different local systems and my
> other container [x237net/alpine-guix] which builds successfully on their
> platform also calls ``guix pull``.

My intuition is that your issue comes from this other container.
And it builds, pulls etc because your are inside. However, if
something is wrong then the command "FROM x237net/alpine-guix" does
not do what you expect.

I mean, if the container x237net/alpine-guix is correct, you should be
able to just run this simple Dockerfile:

FROM x237net/alpine-guix:latest
RUN guix pull

(modulo set the correct paths and maybe start the daemon)


> I guess they are reducing the capabilities allowed to their build platform
> but I can really tell what operation is guix pull attempting in this
> particular case.

Last, aside the "Operation not permitted", check if the network is
correctly setup.


Hope that helps.

All the best,
simon

  parent reply	other threads:[~2020-02-06 14:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-30 13:10 guix pull: error: getting status of /var/guix/gcroots Jimmy Thrasibule
2020-02-06 10:29 ` mlell
2020-02-06 14:02 ` zimoun [this message]
2020-02-06 21:19   ` Jimmy Thrasibule
2020-02-07 12:16     ` zimoun

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='CAJ3okZ3YJt8AuN=JF-fqPcPZMeXJ+2hLWAqr4avUR+RLJUrc2Q@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=jimmy@thrasibule.mx \
    /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).