It started working. I don't know what fixed it but these are what I tried:
1) In Docker Desktop, reset all data to factory defaults
2) Created ubuntu root password and su -
3) Turned off experimental Docker feature "cloud enabled".
4) I found the secret admin password in the Console in Docker
Hello, Anil
Your previous docker command has created a container and that's using that
5 port. Remove that container first then rerun docker command again.
*To list the inactive container:*
docker ps -a
*To rm container:*
docker rm
Regards,
On Wed, Feb 3, 2021 at 11:39 PM Anil
hi Randy
you can create folders and assign permissions to folders as dom dom
suggests. then you can create projects under thisenfolders
On Wed, Feb 3, 2021, 08:21 Dom Dom wrote:
> Did you see the video yet?
> they are so clear for your question
>
> Vào Th 4, 3 thg 2, 2021 vào lúc 08:38 Dom
The earlier instructions had:
*Launching Jenkins can then be accomplished with a simple docker command*
*as the root user (copy/paste to your VM):*
* sudo su -*
* docker run --name jenkins --rm -u root -d -p 8080:8080 -p 5:5 -v
/var/run/docker.sock:/var/run/docker.sock -v
root:/home/jenkins# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED
STATUS PORTS
NAMES
a0c268c14b94 jenkins/jenkins:lts "/sbin/tini -- /usr/…" 4 hours ago
Up 4 hours 0.0.0.0:8080->8080/tcp, 0.0.0.0
The dashboard is
running
docker run \
-u jenkins \
--rm \
-d \
-p 8080:8080 \
-p 5:5 \
-v /var/run/docker.sock:/var/run/docker.sock \
* -v /home/jenkins:/var/jenkins_home \*
jenkins/jenkins:lts
because when I try to run the script in the tutorial, it fails.
*+
I tried again. It is very strange. Now the script works. I did not do
anything differently.
*Started by user jenkins admin*
*Running in Durability level: MAX_SURVIVABILITY*
*[Pipeline] Start of Pipeline*
*[Pipeline] node*
*Running on Jenkins in /var/jenkins_home/workspace/script*
*[Pipeline]
Jenkins 2.263.3 LTS Windows 10 Home Docker Windows Ubuntu
On Wednesday, February 3, 2021 at 9:31:49 PM UTC-6 Anil wrote:
> running
>
>
> docker run \
> -u jenkins \
> --rm \
> -d \
> -p 8080:8080 \
> -p 5:5 \
> -v /var/run/docker.sock:/var/run/docker.sock \
> * -v
I am wondering - should I be running the jenkins scripts in the Docker
Desktop CLI?
I noticed there is a CLI button and when I click it, I get a shell
*#*
*# pwd*
*/*
*# whoami*
*root*
*# ls /var*
*backups cache jenkins_home lib local lock log mail opt run
spool tmp*
*# ls
screenshot:
[image: Capture.JPG]
On Wednesday, February 3, 2021 at 3:31:35 PM UTC-6 Anil wrote:
> root:/home/jenkins# docker ps -a
> CONTAINER ID IMAGE COMMAND CREATED
> STATUS PORTS
> NAMES
> a0c268c14b94 jenkins/jenkins:lts
In my reply above, I posted the command.
I think it may have something to do with the filesystem.
When I cat /home/jenkins/secrets/initialAdminPassword
it cannot find the file.
Is there something I should do to map the drive correctly?
On Tuesday, February 2, 2021 at 9:21:45 PM UTC-6 Mark Waite
In an ubuntu terminal (Windows 10 Home WSL2) I ran the provided code from
the tutorial (Jenkins Essential Training):
I ran it under root
useradd jenkins -m
docker run \
-u jenkins \
--rm \
-d \
-p 8080:8080 \
-p 5:5 \
-v /var/run/docker.sock:/var/run/docker.sock \
-v
Hello
i don't think File Parameters are supported by Jenkins Pipeline
See https://issues.jenkins.io/browse/JENKINS-27413
Regards
On Wednesday, 3 February 2021 at 07:23:51 UTC+1 shif...@gmail.com wrote:
> My Jenkins pipeline runs on the Slave using agent { node { label
> 'slave_node1' } }.
>
>
13 matches
Mail list logo
