When creating the secrets, should create a script that will read these interactively and securely.

Another idea would be to load the credentials from an external service following a public-key encryption scheme. This would be useful in unattended installation scenarios, where there is no user/admin installing this project manually:

• The remote service would return the credentials encrypted.
• The client would decrypt the credentials.

Instead of:

echo "admin" | docker secret create jenkins-user -
echo "admin" | docker secret create jenkins-pass -

Should be (for example):
./docker-create-secret [--just=(user|pass)] [--from-url <uri>] [--key-id <gpg-key>]

This way, there will be no trace of sensitive credentials in the terminal history.

Jesús

Configuración correcta de portainer

Después de iniciar sesión muestra varios fallos de seguridad