starred/mkcert

Fork 0

mirror of https://github.com/FiloSottile/mkcert.git synced 2026-04-25 05:26:03 +03:00

[GH-ISSUE #330] mkcert -install` fails to run on Arch based system #216

New issue

Open

opened 2026-02-25 22:32:52 +03:00 by kerem · 4 comments

kerem commented

2026-02-25 22:32:52 +03:00

Owner

Originally created by @Lvceo on GitHub (Jan 8, 2021).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/330

After installing the necessary package required in the installation note, I run the first command

mkcert -install
ERROR: failed to execute "update-ca-certificates": exec: "update-ca-certificates": executable file not found in $PATH

It seems he is searching for update-ca-certificates command, but Arch is providing a sightly different command to do the same job trust I think this case should be taken into account to make the mkcert -install to run correctly.
Thank you

Originally created by @Lvceo on GitHub (Jan 8, 2021). Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/330 After installing the necessary package required in the installation note, I run the first command ``` mkcert -install ERROR: failed to execute "update-ca-certificates": exec: "update-ca-certificates": executable file not found in $PATH ``` It seems he is searching for update-ca-certificates command, but Arch is providing a sightly different command to do the same job `trust` I think this case should be taken into account to make the `mkcert -install` to run correctly. Thank you

kerem added the

waiting for info

label

2026-02-25 22:32:52 +03:00

kerem commented

2026-02-25 22:32:53 +03:00

Author

Owner

@mikhailal commented on GitHub (Jan 22, 2021):

Has this issue been already solved?

I tried to reproduce this issue with arch 21-01 (latest) running in VirtualBox,
mkcert -install works fine.

Environment:

uname -a:
Linux archiso 5.10.3-arch1-1 #1 PREEMPT Sun, 27 Dec 2020 ...

go version:
go version go1.15.7 linux/amd64

mkcert:
version: 1a5aaff (master)

@mikhailal commented on GitHub (Jan 22, 2021): Has this issue been already solved? I tried to reproduce this issue with arch 21-01 (latest) running in VirtualBox, mkcert -install works fine. Environment: ``` uname -a: Linux archiso 5.10.3-arch1-1 #1 PREEMPT Sun, 27 Dec 2020 ... ``` ``` go version: go version go1.15.7 linux/amd64 ``` ``` mkcert: version: 1a5aaff (master) ```

kerem commented

2026-02-25 22:32:53 +03:00

Author

Owner

@FiloSottile commented on GitHub (Jan 24, 2021):

mkcert supports trust, but it looks like your system also has a different store that is usually managed with update-ca-certificates. If this is a common setup that you can help us reproduce, we can look into handling it better.

github.com/FiloSottile/mkcert@1a5aaff12e/truststore_linux.go (L38-L43)

@FiloSottile commented on GitHub (Jan 24, 2021): mkcert supports `trust`, but it looks like your system also has a different store that is usually managed with `update-ca-certificates`. If this is a common setup that you can help us reproduce, we can look into handling it better. https://github.com/FiloSottile/mkcert/blob/1a5aaff12e0edb54f32ce187079d05c4a1ffd19b/truststore_linux.go#L38-L43

kerem commented

2026-02-25 22:32:53 +03:00

Author

Owner

@jahway603 commented on GitHub (Feb 15, 2021):

I am not the OP, but I also run Arch Linux and was successful using this tool I just discovered today. I installed mkcert using pacman and used mkcert -install to succesfully create cert for a web server I'm using now.

@jahway603 commented on GitHub (Feb 15, 2021): I am not the OP, but I also run Arch Linux and was successful using this tool I just discovered today. I installed mkcert using pacman and used mkcert -install to succesfully create cert for a web server I'm using now.

kerem commented

2026-02-25 22:32:53 +03:00

Author

Owner

@andykais commented on GitHub (May 24, 2021):

I am also running arch linux and I think I see the problem. I did have update-ca-certificates installed, and just started using the new trust command. This folder does exist:

ls -l /usr/local/share/ca-certificates
total 8
-rw-r--r-- 1 root root 1651 May 24 14:47 mkcert_development_CA_325307668194152792698134515606529139355.crt
-rw-r--r-- 1 root root 1168 Apr 19 10:49 RootCA.pem

I followed the instructions here https://archlinux.org/news/ca-certificates-update/ (most importantly moving /usr/local/share/ca-certificates/*.crt to /etc/ca-certificates/trust-source/anchors/) and then removed /usr/local/share/ca-certificates. Everything seems to work fine now, but I think this could be seamless if mkcert just prioritizes the trust command over update-ca-certificates if trust is available.

@andykais commented on GitHub (May 24, 2021): I am also running arch linux and I think I see the problem. I did have `update-ca-certificates` installed, and just started using the new `trust` command. This folder does exist: ``` ls -l /usr/local/share/ca-certificates total 8 -rw-r--r-- 1 root root 1651 May 24 14:47 mkcert_development_CA_325307668194152792698134515606529139355.crt -rw-r--r-- 1 root root 1168 Apr 19 10:49 RootCA.pem ``` I followed the instructions here https://archlinux.org/news/ca-certificates-update/ (most importantly moving `/usr/local/share/ca-certificates/*.crt` to `/etc/ca-certificates/trust-source/anchors/`) and then removed `/usr/local/share/ca-certificates`. Everything seems to work fine now, but I think this could be seamless if mkcert just prioritizes the `trust` command over `update-ca-certificates` if `trust` is available.

kerem referenced this issue

2026-02-25 22:33:26 +03:00

[PR #216] [MERGED] truststore_nss: retry certtool with sudo when it fails due to permissions #416