PavelSosin-320

Results 40 comments of PavelSosin-320

@Chuxel How-to: correctly deploy dev container to managed Swarm cluster(*) 0. Enable Swarm mode in Docker Desktop and init Swarm - docker swarm init 1. Deploy registry;2 image as localhost:5000...

Vote for this !!!! A similar feature is a fundamental feature for remote maintenance, Test automation, and IT automation ( Ansible). For example, automatic tests must run under user by...

Do you actually ask how to monitor and manage resource consumption by NODEJS? This is not a VSCODE topic and the answer can be found in discussions about the deployment...

@haircommander Now conmon 2.1 tries to write messages to **DEBU[0000] /usr/bin/conmon messages will be logged to syslog** DEBU[0000] running conmon: /usr/bin/conmon args="[--api-version 1 -c d8db6db55eff0baf9291c7e88eb475c5571b283ce572984bad82b878f6dee7d7 -u d8db6db55eff0baf9291c7e88eb475c5571b283ce572984bad82b878f6dee7d7 -r /usr/bin/crun -b...

@haircommander I observe the Podman container start issue that appears from Podman version 3.4.4 on Fedora 35 workstation with BTRFS and GNome 4, naturally. At the same time Journal logs...

@haircommander After full cleanup and rerunning of podman start I found that the issue is actually dup of #https://github.com/containers/conmon/issues/67. Starting from Fedora, up to 34 Fedora had no syslog driver...

@haircommander Note: conmon and crun need certain capabilities to be able writing into syslog. It's allowed only to root by the default (*). Both files have no caps xattributes and...

The bright side: the cause of the error is keeping Windows user when login in Linux. Linux session is created by pam only after user and password prompts have been...

@crramirez The solution is: after Initialization using genie -s I use Windows terminal with multiple sessions started by the command line wsl ... -u root genie -l login: ... password:...

@crramirez PR for WSL Kernel - based on Fedora Magazine announcement #https://github.com/microsoft/WSL/issues/6757