Cannot install cockpit-docker

[mirto]

Hi all,
I’m trying to install cockpit-docker but I receive a package invalid or corrupt error
(strangely LANG=C has no effect)

Here the transcript:

LANG=C pamac install cockpit-docker                                                                                                                                                                                 ✔  mirto@nfs-vm 
Preparing...
==== AUTHENTICATING FOR org.manjaro.pamac.commit ====
Authentication is required to install, update, or remove packages
Authenticating as: Mirto (mirto)
Password: 
==== AUTHENTICATION COMPLETE ====
Sincronizzazione database dei pacchetti...
Resolving dependencies...
Checking inter-conflicts...

To install (4):
  runc            1.4.0-1     (Required By: cockpit-docker)  extra  
  containerd      2.2.1-1     (Required By: cockpit-docker)  extra  
  docker          1:29.2.0-1  (Required By: cockpit-docker)  extra  
  cockpit-docker  16-2                                       extra  660,3 kB

Total download size: 660,3 kB
Total installed size: 221,1 MB

Apply transaction ? [y/N] y
Download di cockpit-docker (16-2) iniziato                                                                                                                                                                                                        
Download di cockpit-docker (16-2) terminato                                                                                                                                                                                                       
Controllo portachiavi...                                                                                                                                                                                                                     [4/4]
Verifico l'integrità dei pacchetti...                                                                                                                                                                                                        [4/4]
Errore: cockpit-docker: la firma di "Morgan Adamiec <morganamilo@archlinux.org>" ha un'affidabilità marginale
Rimuovi i file non validi e riprova ...
Risoluzione delle dipendenze...
Controllo conflitti tra i pacchetti...
Download di cockpit-docker (16-2) iniziato                                                                                                                                                                                                        
Download di cockpit-docker (16-2) terminato                                                                                                                                                                                                       
Controllo portachiavi...                                                                                                                                                                                                                     [4/4]
Verifico l'integrità dei pacchetti...                                                                                                                                                                                                        [4/4]
Errore: cockpit-docker: la firma di "Morgan Adamiec <morganamilo@archlinux.org>" ha un'affidabilità marginale
Error: Inizializzazione del trasferimento non riuscita.: il pacchetto non è valido oppure è corrotto (firma PGP):

What I’m doing wrong?

[Aragorn]

See if this may help…

• [root tip] [How To] Mitigate and prevent GPGME error when syncing your system

[Lolix]

Do you have archlinux-keyring updated?

[linux-aarhus]

@mirto

What I’m doing wrong?

Why are you using the docker image?

[root tip] [How To] Manjaro NAS (Network Attached Storage) service

Simple Manjaro NAS This is a short guide showing how you can add NAS filesharing capabilities to a running Manjaro installation thus adding simple NAS functionality. prepare your system The first step is mandatory - to ensure the system is fully up-to-date sudo pacman -Syu This little project will use the web-based cockpit administration application. This application is maintained by Red Hat developers - so all documentation inside the app is pointing to Red Hat documentation. Cockpit is a m…

[mirto]

No, I didnt check.
Should I issue

sudo pacman -S manjaro-keyring
sudo pacman-key --populate manjaro

to be safe?

[mirto]

Well, no.
I installed the packages from the pamac gui and I took the packages list from https://wiki.archlinux.org/title/Cockpit

All installed correctly except cockpit-docker

The tutorial in the forum is very useful.

BTW I gave up cockpit because I didn’t found any method in cockpit to restrict access to the 9090 port.
The only solution I found is setting up firewalld rules.

For now I setup a Majaro nfs server and I’m looking for a web management interface less invasive than cockpit. (but this is another thread)

Thanks a lot.

[linux-aarhus]

@mirto

For now I setup a Majaro nfs server and I’m looking for a web management interface less invasive than cockpit.

Less invasive?

I cannot imagine any web management interface to be lesser invasive as cockpit.

@mirto

I gave up cockpit because I didn’t found any method in cockpit to restrict access to the 9090 port.

Why would you need to restrict it?

If the user has no admin rights (wheel group) then they only have limited access.

[mirto]

Well @linux-aarhus sorry to bother you with stupid questions.

TL;DR

About a less invasive web management interface, as an example, in the old days I used WEBMIN; but I don’t like the stack used (I don’t like PHP even if I used it many times)

About the access restriction it is complicated question. I tried to keep the questions as simple as possible; but to explain my mind here is my use case:

• two connected lans
• an ISP router that manages port-forwarding and have an external fixed address
• a home server up H24 (mainly as monitoring ISP line via smokeping and as an internal NFS server). It also manages some KVM virtual machines, all communicating through the bridge defined on the first server network card
• 2 other computers and 3 laptop

For security a webcam and a little nas (qnap) was installed.
Now the nas hard disk died. So I decided to create a VM to replace the died nas.

The webcam only needs an nfs share. So I setup a VM with nfs.
For me limiting access to a nfs share is simple: declare the network you want to allow and decide if ro or rw.

The first attempt was using OpenMediaVault on a vm. I was lost in the attempt to assign the ro/rw access to the nfs share.

Due to the fact I don’t need an all-round nas software, I decided to use an nfs server with a web management interface.

As web interface I tried cockpit (overwhelming but should work) then I discovered that to limit access to the management interface I should use firewalld.
My firewalld configuration is not that simple and the server and the vm use the same bridge. In this case I suppose that to restrict the nfs service to the 2 local lan is using the rich-rules (I don’t like rich-rules).

Then I’ll look for a simpler web interface

Hope this clarified my … madness

P.S. if you are curious about the 3 pc, 3 laptop, 3 smartphone, the answer is: me, my wife and my son

[linux-aarhus]

@mirto

The webcam only needs an nfs share. So I setup a VM with nfs.
For me limiting access to a nfs share is simple: declare the network you want to allow and decide if ro or rw.

I see - then you don’t need a management interface - nfs is the simplest sharing mechanism - especially when no Windows system involved.