Перейти к содержимому

08-Trouble shooting continues -important catch in description

Devops init

0:00 / 0:00

08-Trouble shooting continues -important catch in description

4 просмотра · 12 дн. назад
Devops init
85 подписчиков
4 просмотра · 12 дн. назад
The error chown: invalid user: 'jenkins:jenkins' occurs because the jenkins user and group do not exist on this Linux instance (node-dockerhost). Root Cause You are SSH'd into an EC2 instance (node-dockerhost) that acts as a worker agent or remote host, where Jenkins itself is likely running on a different server or container, or Jenkins hasn't been installed on this host. Because the OS has no jenkins user in /etc/passwd, Linux cannot assign file ownership to it. Solutions Solution: Keep Ownership as ec2-user (Recommended for Agent Hosts) If this host is a Jenkins build agent or remote deployment host where SSH commands are executed as ec2-user, leave ownership as ec2-user:ec2-user (which you already successfully set earlier in your terminal session): sudo chown -R ec2-user:ec2-user /opt/jenkins/workspace Verification: Run ls -ld /opt/jenkins/workspace. It should display ec2-user ec2-user as owner and group.