#Dangerzone not installing

1 messages · Page 1 of 1 (latest)

jagged halo
#

hi, idk why but dangerzone is failing to install: ```ujust install-dangerzone
Warning: Dangerzone (https://dangerzone.rocks/) requires enabling both
container-domain user namespace creation and (restricted) ptrace. This
is a security tradeoff, as other programs on your system will also be
able to use container tools such as podman and to use ptrace to
inspect child processes.

Continue installing Dangerzone? [y/n] y
Enabling Dangerzone repository...
Ensuring ptrace is allowed...
Setting container policy to allow Dangerzone...
Enabling container-domain user namespace creation...
Container-domain user namespace creation is already enabled.
Installing Dangerzone as layered package...
Checking out tree abd3076... done
Enabled rpm-md repositories: dangerzone fedora-multimedia updates fedora secureblue copr:copr.fedorainfracloud.org:secureblue:branding copr:copr.fedorainfracloud.org:secureblue:bubblejail copr:copr.fedorainfracloud.org:secureblue:crane copr:copr.fedorainfracloud.org:secureblue:hardened_malloc copr:copr.fedorainfracloud.org:secureblue:homebrew copr:copr.fedorainfracloud.org:secureblue:no_rlimit_as copr:copr.fedorainfracloud.org:secureblue:run0edit copr:copr.fedorainfracloud.org:secureblue:slsa-verifier updates-archive
Updating metadata for 'updates'... done
error: Updating rpm-md repo 'updates': cannot update repo 'updates': Cannot prepare internal mirrorlist: Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject.org/metalink?protocol=https&repo=updates-released-f43&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org]; Last error: Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject.org/metalink?protocol=https&repo=updates-released-f43&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org]
error: Recipe install-dangerzone failed with exit code 1

rustic ridge
#

that looks like a transient network issue, just try again

jagged halo
#

Thx

solid thicket
rustic ridge
#

it might be a DNS issue or might be a server issue

#

hard to say