unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Jimmy Thrasibule <jimmy.thrasibule@gmail.com>
To: help-guix <help-guix@gnu.org>
Subject: Re: guix pull: error: getting status of /var/guix/gcroots
Date: Thu, 6 Feb 2020 22:19:40 +0100	[thread overview]
Message-ID: <CAMqSRmCQcPftirHpJSQudSNW=8gTamOHK5MQXgerBdMP9z_jSg@mail.gmail.com> (raw)
In-Reply-To: <CAJ3okZ3YJt8AuN=JF-fqPcPZMeXJ+2hLWAqr4avUR+RLJUrc2Q@mail.gmail.com>

> Do you have any possibility to run guix pull with strace?

Unfortunately containers are not given PTRACE privileges during the
build phase so I cannot call strace.

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

Well the folder exists and is owned by root.

> 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.

The x237net/guixsd container builds successfully on my work stations
and others. Only hub.docker.com CI's platform seems to fail building
the image. I actually pushed to the hub an image that I successfully
built.

  reply	other threads:[~2020-02-06 21:19 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
2020-02-06 21:19   ` Jimmy Thrasibule [this message]
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='CAMqSRmCQcPftirHpJSQudSNW=8gTamOHK5MQXgerBdMP9z_jSg@mail.gmail.com' \
    --to=jimmy.thrasibule@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).