From: Jimmy Thrasibule <jimmy.thrasibule@gmail.com>
To: help-guix@gnu.org
Subject: Re: guix pull: error: symlink: File exists
Date: Sun, 19 Jan 2020 19:54:00 +0100 [thread overview]
Message-ID: <CAMqSRmAQE08uHtAhm=p62YmBBtEGj6KJSvxRx+ou+4szw5jZhQ@mail.gmail.com> (raw)
In-Reply-To: <CAMqSRmAhD7NRtNtO09G6uSRgs02AtQKisDCG6Ojt=WtQK=Oogg@mail.gmail.com>
I tried some actions and here is what happening:
# ls -l .config/guix/
total 0
lrwxrwxrwx 1 root root 45 Jan 19 18:33 current ->
/var/guix/profiles/per-user/root/current-guix
# guix pull
Migrating profile generations to '/var/guix/profiles/default'...
Updating channel 'guix' from Git repository at '
https://git.savannah.gnu.org/git/guix.git'...
[...]
When ``.config/guix/current`` is pointing to
``/var/guix/profiles/per-user/root/current-guix``, the ``guix pull``
command will change the link to `` /var/guix/profiles/default`` or the
other way arround.
Calling ``guix pull`` again will fail:
# ls -l .config/guix/
total 0
lrwxrwxrwx 1 root root 39 Jan 19 18:37 current ->
/var/guix/profiles/default/current-guix
# guix pull
Migrating profile generations to '/var/guix/profiles/per-user/root'...
guix pull: error: symlink: File exists:
"/var/guix/profiles/per-user/root/current-guix"
The workaround is to link back the profile to ``per-user/root`` and delete
``/var/guix/profiles/default/current-guix*``.
It is not clear why Guix is constantly swapping the profiles this way.
Le sam. 18 janv. 2020 à 22:11, Jimmy Thrasibule <jimmy.thrasibule@gmail.com>
a écrit :
> Hi,
>
> I'm working on an Alpine Docker image with the Guix package manager [1].
> The container is building and can run Guix without the ``--privileged``
> option.
>
> The installation process is based on the documentation and the
> installation script [2]. Everything is working fine however, when I run
> ``guix pull`` in the generated image, I got the following error:
>
>
> Migrating profile generations to '/var/guix/profiles/per-user/root'...
> guix pull: error: symlink: File exists: "
> /var/guix/profiles/per-user/root/current-guix"
>
>
> This issue has already been discussed at [3] but the workaround to delete
> all the links in the directory ``/var/guix/profiles/per-user/root`` is
> causing some troubles:
>
> 1. If I want to ship a ready to use image and delete the links upfront,
> ``guix daemon`` will fail to start since ``/root/.config/guix/current`` is
> broken.
> 2. Users of the image can delete the links themselves but this is not
> really friendly.
>
> So what is exactly causing this error and what would be a good option to
> fix it?
>
>
> [1] https://hub.docker.com/repository/docker/x237net/alpine-guix
> [2] https://git.savannah.gnu.org/cgit/guix.git/plain/etc/guix-install.sh
> [3] https://lists.gnu.org/archive/html/help-guix/2018-12/msg00098.html
>
>
next prev parent reply other threads:[~2020-01-19 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-18 21:11 guix pull: error: symlink: File exists Jimmy Thrasibule
2020-01-19 18:54 ` Jimmy Thrasibule [this message]
2020-01-20 9:29 ` Jimmy Thrasibule
2020-01-20 17:21 ` 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='CAMqSRmAQE08uHtAhm=p62YmBBtEGj6KJSvxRx+ou+4szw5jZhQ@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).