I am new in Auto.Tester and I don't know why aerokube/selenoid 1.10.8 useing the old version of chrome (102).
I have updated chrome to 103 and 104, with:
cm selenoid update --vnc
I have tried edit "browsers" file, where default chrome browser is 104,
{
"chrome": {
"default": "104.0",
"versions": {
"102.0": {
"image": "selenoid/chrome:102.0",
"port": "4444",
"path": "/"
},
"104.0": {
"image": "selenoid/chrome:104.0",
"port": "4444",
"path": "/"
}
}
},
and run
kill -s HUP selenoid
(I tried kill docker and run it again), if in Jenkins I start the tests, then in Docker-logs I got:
[LOCATING_SERVICE] [chrome] [102.0]
[ENVIRONMENT_NOT_AVAILABLE] [chrome] [102.0]
but why ? my docker images already installed
selenoid/chrome 104.0 fbfc55ec3a1d 18 days ago 1.14 GB
selenoid/chrome 103.0 bae72cc83bc2 29 days ago 1.13 GB
selenoid/chrome 102.0 521a0d311b8c 3 months ago 1.12 GB
Should I edit some config file ?
chromedriver is in version: Starting ChromeDriver 104.0.5112.79 (3cf3e8c8a07d104b9e1260c910efb8f383285dc5-refs/branch-heads/5112#{#1307})
(http://localhost:4444/status: {"total":6,"used":0,"queued":0,"pending":0,"browsers":{"chrome":{"102.0":{},"104.0":{}},"firefox":{"102.0":{},"103.0":{}},"opera":{"86.0":{},"88.0":{}}}})
Related
I can't get Jenkins to deploy a war file on a Tomcat8 server. Why can't Jenkins deploy to Tomcat?
when I run the Jenkins job, I got this exception:
[DeployPublisher][INFO] Deploying /var/jenkins_home/workspace/Deploy_to_Tomcat_server/webapp/target/webapp.war to container Tomcat 8.x Remote with context null
ERROR: Build step failed with exception
java.net.ConnectException: Connection refused (Connection refused)
I think it has to be a problem with both docker containers, so I will describe what I have done.
Both Jenkins servers and Tomcat8 are running on my local machine in docker containers. So that both can see each other, I have created a common network.
~ % docker network ls
NETWORK ID NAME DRIVER SCOPE
da6fc157710c bridge bridge local
...
// network bridge already exists!
~ % docker network create --driver bridge my_jenkins_tomcat_network
378ef3f01e215207e90ca0a6e93e89a9610be1e9bd972f94f02f9b1ce6199923
**// Run jenkins container**
~ % docker run -d -p 8080:8080 --name jenkins_container_test --network my_jenkins_tomcat_network jenkinsci/blueocean
08a2ce5e609f0c50e3a4c9ce73a5c88918e6a0ab69c582d75bc44162ae7e58fd
**// Run tomcat container. I had an image name mywebapp with Tomcat8...**
~ % docker run -d -p 80:8080 --name tomcat_container_test --network my_jenkins_tomcat_network mywebapp
5ac868dbeb69512c7c2d5b62f067de72592a01e763cf5b20808d22c06de1fe0e
~ % docker container ls
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
5ac868dbeb69 mywebapp "catalina.sh run" 9 seconds ago Up 8 seconds 0.0.0.0:80->8080/tcp tomcat_container_test
08a2ce5e609f jenkinsci/blueocean "/sbin/tini -- /usr/…" About a minute ago Up About a minute 0.0.0.0:8080->8080/tcp, 50000/tcp jenkins_container_test
I can inspect both containers and the new network:
~ % docker network ls
NETWORK ID NAME DRIVER SCOPE
da6fc157710c bridge bridge local
378ef3f01e21 my_jenkins_tomcat_network bridge local
~ % docker inspect my_jenkins_tomcat_network
[
{
"Name": "my_jenkins_tomcat_network",
"Id": "378ef3f01e215207e90ca0a6e93e89a9610be1e9bd972f94f02f9b1ce6199923",
"Created": "2021-04-12T08:07:52.770548349Z",
"Scope": "local",
"Driver": "bridge",
"EnableIPv6": false,
"IPAM": {
"Driver": "default",
"Options": {},
"Config": [
{
"Subnet": "172.23.0.0/16",
"Gateway": "172.23.0.1"
}
]
},
"Internal": false,
"Attachable": false,
"Ingress": false,
"ConfigFrom": {
"Network": ""
},
"ConfigOnly": false,
"Containers": {
"08a2ce5e609f0c50e3a4c9ce73a5c88918e6a0ab69c582d75bc44162ae7e58fd": {
"Name": "**jenkins_container_test**",
"EndpointID": "80adf0fe02288d76f24e675ad0fdf25bf89ac64ac135dee03cdd4b91a74a6d3e",
"MacAddress": "02:42:ac:17:00:02",
"IPv4Address": "**172.23.0.2/16**",
"IPv6Address": ""
},
"5ac868dbeb69512c7c2d5b62f067de72592a01e763cf5b20808d22c06de1fe0e": {
"Name": "**tomcat_container_test**",
"EndpointID": "ca216dc9302db6eee66393d9210aab4e4236c7442dba5c3701bcebc11b2e9463",
"MacAddress": "02:42:ac:17:00:03",
"IPv4Address": "**172.23.0.3/16**",
"IPv6Address": ""
}
},
"Options": {},
"Labels": {}
}
]
I can exec bash in Jenkins container and ping tomcat container:
~ % docker container ls
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
5ac868dbeb69 mywebapp "catalina.sh run" About an hour ago Up About an hour 0.0.0.0:80->8080/tcp tomcat_container_test
08a2ce5e609f jenkinsci/blueocean "/sbin/tini -- /usr/…" About an hour ago Up About an hour 0.0.0.0:8080->8080/tcp, 50000/tcp jenkins_container_test
~ % docker exec -it -u:root 08a2ce5e609f bashh
OCI runtime exec failed: exec failed: container_linux.go:370: starting container process caused: exec: "bashh": executable file not found in $PATH: unknown
aironman#MacBook-Pro-de-Alonso ~ % docker exec -it -u:root 08a2ce5e609f bash
bash-5.0# ping 172.23.0.3
PING 172.23.0.3 (172.23.0.3): 56 data bytes
64 bytes from 172.23.0.3: seq=0 ttl=64 time=0.163 ms
64 bytes from 172.23.0.3: seq=1 ttl=64 time=0.139 ms
...
In my tomcat container, I have modified tomcat-users.xml file with this default content:
<role rolename="manager-gui"/>
<role rolename="manager-script"/>
<role rolename="manager-jmx"/>
<role rolename="manager-status"/>
<user username="tomcat" password="tomcat" roles="manager-gui"/>
<user username="admin" password="admin" roles="manager-gui,manager-script,manager-jmx,manager-status"/>
**<user username="deployer" password="deployer" roles="manager-script"/>**
When I create the Jenkins job, I use the credential deployer and tomcat url as shown above
I have tried too with internal ip, 172.23.0.3, no luck.
I have read this link, without responses, and it is bit different, so I think it is legitimate to answer the question.
One way to achieve this goal is to install this plugin , configure sshd in tomcat container and create a post task in Jenkins in order to copy the war file to webapps folder.
I am trying to configure docker-compose to use different network range by default, so I follow instructions from https://github.com/moby/moby/pull/29376
However, I get following error:
unable to configure the Docker docker daemon with file
/etc/docker/daemon.json: the following directives don't match any
configuration option: default-address-pools
Here is the content of daemon.json - it is the sample taken from the #29376.
{
"default-address-pools": [
{
"scope": "local",
"base": "172.80.0.0/16",
"size": 24
},
{
"scope": "global",
"base": "172.90.0.0/16",
"size": 24
}
]
}
Please advise.
My env:
# uname -a
Linux gfn-classroom 4.4.0-109-generic #132-Ubuntu SMP Tue Jan 9 19:52:39 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
# docker --version
Docker version 17.12.0-ce, build c97c6d6
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
This is merged in https://github.com/moby/moby/pull/36396 and (hopefully) will be available in 18.06. [Reference]
Also note changing default address pool is also available as a cli argument, e.g.:
/usr/bin/dockerd -H ... --default-address-pool base=172.29.0.0,size=16
Pull-request https://github.com/moby/moby/pull/29376 was closed, not merged, so that feature is not available (yet) in Docker
When I try to run any container on Docker on Windows I get the following error.
docker: Error response from daemon: container
70518b4959aca4092b2f65c0881a6c25851789656e3d7ce2610e6322b32aeffe
encountered an error during CreateContainer: failure in a Windows
system call: The system cannot find the path specified. (0x3) extra
info:
{
"SystemType": "Container",
"Name": "70518b4959aca4092b2f65c0881a6c25851789656e3d7ce2610e6322b32aeffe",
"Owner": "docker",
"IgnoreFlushesDuringBoot": true,
"LayerFolderPath": "C:\\ProgramData\\Docker\\windowsfilter\\70518b4959aca4092b2f65c0881a6c25851789656e3d7ce2610e6322b32aeffe",
"Layers": [
{
"ID": "db3c3c75-2b7c-5d4a-bde3-463ffc817a5b",
"Path": "C:\\ProgramData\\Docker\\windowsfilter\\61ad8a0caffe153621375482f419c592edaade796b909edd8a7edda142818414"
},
{
"ID": "3e2f377e-6c2f-5b95-9e80-fceef67d4b01",
"Path": "C:\\ProgramData\\Docker\\windowsfilter\\54a8c9c1afb96bd64a3dd69f0f84aee1eaf18644791cf2812caeab26adf12632"
}
],
"HostName": "70518b4959ac",
"HvPartition": true,
"EndpointList": [
"36bbd687-56fb-4281-a9ee-4f81dcb5a795"
],
"HvRuntime": {
"ImagePath": "C:\\ProgramData\\Docker\\windowsfilter\\61ad8a0caffe153621375482f419c592edaade796b909edd8a7edda142818414\\UtilityVM"
},
"AllowUnqualifiedDNSQuery": true
}.
I believe the error could be related to the underlying hyper-v settings as I received the same error with a brand new vanilla Hyper-V VM set with just a mounted bootable iso disc.
Here is the docker info
Version: 17.11.0-ce-rc3-win38 (14052)
Channel: edge
Sha1: 32de2331204faa0f33731efe56df79e713ee0fba
Started on: 2017/11/15 22:37:53.300
Resources: C:\Program Files\Docker\Docker\Resources
OS: Windows 10 Enterprise
Edition: Enterprise
Id: 1709
Build: 16299
BuildLabName: 16299.15.amd64fre.rs3_release.170928-1534
Steps I have tried all resulting in the same:
1) Install Docker Edge
2) Uninstall and Reinstall Docker
3) Uninstall Hyper-V and reinstall
4) Changing the Hyper-V Storage locations
when i created the network,it can work properly.
[root#localhost ~]# docker run --net=br1 --ip=192.168.0.119 -ti --name=doc 328edcd84f1b /bin/bash
[root#8f5c0179d86a /]# ping www.baidu.com
PING www.a.shifen.com (115.239.210.27) 56(84) bytes of data.
64 bytes from 115.239.210.27 (115.239.210.27): icmp_seq=1 ttl=55 time=10.8 ms
but when i reboot the host(or restart the docker),it failed to start containers
I display the list of networks, it is there,but the error message tells me that it does not exist
my docker version is 1.12.6
[root#localhost ~]# docker network ls
NETWORK ID NAME DRIVER SCOPE
e83fa9afc6af br1 bridge local
2fb7bed3e5ba bridge bridge local
984a5e65f182 host host local
d8e8ce860225 none null local
[root#localhost ~]#
[root#localhost ~]#
[root#localhost ~]# docker network inspect br1
[
{
"Name": "br1",
"Id": "e83fa9afc6af2cf01b0b0103d0c98d7334717cdd5290e2121dc03a5d6b48aa84",
"Scope": "local",
"Driver": "bridge",
"EnableIPv6": false,
"IPAM": {
"Driver": "default",
"Options": {},
"Config": [
{
"Subnet": "192.168.0.0/24",
"IPRange": "192.168.0.0/24",
"Gateway": "192.168.0.120"
}
]
},
"Internal": false,
"Containers": {},
"Options": {
"com.docker.network.bridge.name": "br0",
"parent": "ens33"
},
"Labels": {}
}
]
[root#localhost ~]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
8f5c0179d86a 328edcd84f1b "/bin/bash" 2 hours ago Exited (137) 56 minutes ago doc
2492467008a0 328edcd84f1b "/bin/bash" 2 hours ago Exited (127) 2 hours ago mytest1
a3c7184a4bf5 328edcd84f1b "/bin/bash" 17 hours ago Exited (0) 17 hours ago awesome_perlman
f1e26864c870 328edcd84f1b "/bin/bash" 18 hours ago Exited (128) 17 hours ago berserk_kalam
ce2d1b7a6ce2 328edcd84f1b "/bin/bash" 18 hours ago Exited (1) 2 hours ago lonely_banach
[root#localhost ~]# docker start doc
Error response from daemon: failed to create endpoint doc on network br1: network e83fa9afc6af2cf01b0b0103d0c98d7334717cdd5290e2121dc03a5d6b48aa84 does not exist
Error: failed to start containers: doc
I have setup Marathon and Mesos on two of my machines.
I can successfully schedule commands from the marathon web console, but when I try to schedule a job involving docker images I immediately get job failed. Plus I get no stderr or stdout files.
Example Running a normal command:
Marathon job conf:
{
"id": "testecho",
"cmd": "echo hello; sleep 10",
"cpus": 1,
"mem": 128,
"disk": 0,
"instances": 1
}
On mesos I see that the tasks have succeeded. I have the stderr and stdout files like normal.
But now if I run a simple docker image task:
Marathon job conf:
{
"id": "/ubuntu",
"cmd": "date -u +%T",
"cpus": 0.5,
"mem": 512,
"disk": 0,
"instances": 1,
"container": {
"type": "DOCKER",
"volumes": [],
"docker": {
"image": "libmesos/ubuntu",
"network": null,
"portMappings": null,
"privileged": false,
"parameters": [],
"forcePullImage": false
}
},
"portDefinitions": [
{
"port": 10001,
"protocol": "tcp",
"labels": {}
}
]
}
On mesos, I see that it has instantly failed:
And I have no stderr or stdout files:
I also notice that on both my machines, when I run:
docker ps -a
I see nothing on both the machines. So that would mean that the docker jobs were not even launched
What could be affecting docker deployment?
The one reason I can think of is that the user that marathon uses to launch tasks not have access to docker? How do I test this?
I noticed that when I run the command:
sudo cat /etc/passwd
I see a user zookeeper. Maybe this is the user that doesn't have access to docker?
But when i do:
su zookeeper
I don't change user profiles
After going through a few tutorials I found the answer from the following tutorial: http://frankhinek.com/deploy-docker-containers-on-mesos-0-20/
I had to enable Docker Containerizer on my mesos-slaves
Set the --containerizers=docker,mesos" command line parameter:
echo "docker,mesos" | sudo tee /etc/mesos-slave/containerizers
Increase the executor timeout to 5 minutes1: (i guess this is optional)
echo "5mins" | sudo tee /etc/mesos-slave/executor_registration_timeout
Restart the Mesos Slave:
sudo service mesos-slave restart