> Other said, how can I reproduce the behaviour you are observing? # Download requirements
$ mkdir -p /tmp/guix-docker $ wget -O /tmp/guix-docker/Dockerfile https://raw.githubusercontent.com/rockandska/.dotfiles/084b3c6924eeb985cb40edfc90e3827b10ba61e2/.local/opt/dotfiles-bootstrap/tests/Dockerfiles/Dockerfile $ wget -O /tmp/guix-docker/build.sh https://raw.githubusercontent.com/rockandska/.dotfiles/084b3c6924eeb985cb40edfc90e3827b10ba61e2/.local/opt/dotfiles-bootstrap/tests/Dockerfiles/hooks/build $ chmod +x /tmp/guix-docker/build.sh $ cd /tmp/guix-docker # it will create two docker image : guix:1.0.1 and guix:latest /tmp/guix-docker $ ./build.sh # start two container with the guix daemon as main process /tmp/guix-docker $ docker run -d -ti --name guix-test-1.0.1 guix:1.0.1 /tmp/guix-docker $ docker run -d -ti --name guix-test-latest guix:latest # install some useful tools /tmp/guix-docker $ docker exec -i guix-test-1.0.1 apk add util-linux /tmp/guix-docker $ docker exec -i guix-test-latest apk add util-linux # compare some things # sh automatically load /root/.guix-profile/etc/profile and is the reason we don't call guix directly /tmp/guix-docker $ sdiff <(docker exec -i guix-test-1.0.1 sh <<<"env") <(docker exec -i guix-test-latest sh <<<"env") /tmp/guix-docker $ sdiff <(docker exec -i guix-test-1.0.1 sh <<<"guix --version") <(docker exec -i guix-test-latest sh <<<"guix --version") /tmp/guix-docker $ sdiff <(docker exec -i guix-test-1.0.1 sh <<<"guix-daemon --version") <(docker exec -i guix-test-latest sh <<<"guix-daemon --version") /tmp/guix-docker $ sdiff <(docker exec -i guix-test-1.0.1 sh <<<"namei /root/.config/guix/current") <(docker exec -i guix-test-latest sh <<<"namei /root/.config/guix/current") /tmp/guix-docker $ sdiff <(docker exec -i guix-test-1.0.1 sh <<<"guix gc --list-roots") <(docker exec -i guix-test-latest sh <<<"guix gc --list-roots") Regards,
