Rancher Server Deployment

-
Make sure you have a clean host with docker daemon installed, then simply run

[root@msdlva-dsnsmt43 tmp]# docker run -d --restart=unless-stopped -p 80:80 -p 443:443 -v /opt/rancher:/var/lib/rancher rancher/rancher:latest
Unable to find image 'rancher/rancher:latest' locally
latest: Pulling from rancher/rancher
22e816666fd6: Pull complete
079b6d2a1e53: Pull complete
11048ebae908: Pull complete
c58094023a2e: Pull complete
8a37a3d9d32f: Pull complete
e403b6985877: Pull complete
9acf582a7992: Pull complete
bed4e005ec0d: Pull complete
74a2e9817745: Pull complete
322f0c253a60: Pull complete
883600f5c6cf: Pull complete
ff331cbe510b: Pull complete
e1d7887879ba: Pull complete
5a5441e6019b: Pull complete
Digest: sha256:f8751258c145cfa8cfb5e67d9784863c67937be3587c133288234a077ea386f4
Status: Downloaded newer image for rancher/rancher:latest
bc28ec5b6222709ec27d03b3c9c1b720d6381431925d5ffa2596ba974671d1bb
[root@msdlva-dsnsmt43 tmp]# docker logs --tail 10 -f bc2
2019/11/15 20:14:39 [INFO] update kontainerdriver huaweicontainercloudengine
2019/11/15 20:14:44 [INFO] kontainerdriver googlekubernetesengine listening on address 127.0.0.1:33293
2019/11/15 20:14:44 [INFO] kontainerdriver googlekubernetesengine stopped
2019/11/15 20:14:44 [INFO] kontainerdriver azurekubernetesservice listening on address 127.0.0.1:35948
2019/11/15 20:14:44 [INFO] update kontainerdriver googlekubernetesengine
2019/11/15 20:14:44 [INFO] kontainerdriver azurekubernetesservice stopped
2019/11/15 20:14:44 [INFO] kontainerdriver amazonelasticcontainerservice listening on address 127.0.0.1:45108
2019/11/15 20:14:44 [INFO] kontainerdriver amazonelasticcontainerservice stopped
2019/11/15 20:14:44 [INFO] update kontainerdriver azurekubernetesservice
2019/11/15 20:14:44 [INFO] update kontainerdriver amazonelasticcontainerservice
2019/11/15 20:14:49 [INFO] kontainerdriver googlekubernetesengine listening on address 127.0.0.1:34310

Comments

Post a Comment

Popular posts from this blog

MongoDB tip: 4 ways to modify replica set configuration

-
This is just a quick guide on how to modify your replica set settings in 4 different ways. This guide is assuming you have a functional replica set ready, it doesn't matter if it's a single node or multi-node replica set. In each of the four method, I am looking to modify the priority of the _id=0 node Method 1: Via Mongo Shell Login to your Mongo shell,  simply type in mongo , assuming default port is being used and authentication is not enabled [in Mongo shell] cfg = rs.conf() cfg.members[0].priority=99 rs.reconfig(cfg) # "ok":1 indicates the new configuration has been set  MongoDB Enterprise minvera:PRIMARY> rs.reconfig(cfg) {         "ok" : 1,         "operationTime" : Timestamp(1528464949, 1),         "$clusterTime" : {                 "clusterTime" : Timestamp(1528464949, 1),                 "signature" : {                         "hash" : BinData(0
Read more

MongoDB Quick Note: BI Connector Issue

-
This is just a quick note of what can stop mongosqld from working properly that I wasn't aware of. Background: My work runs everything mongodb inside of docker containers, so sometimes it's not as straight forward to see immediately of what's preventing your container from working properly What happened: I ran into issue that my container does not stay up after I updated my drdl to reflect new fields introduced to the underlying collection. How to debug: Go to the host server, copy out entrypoint.sh and add sleep 100000000 to before mongosqld is executed. This force the container to stay up for us to look into issue. Cause of the issue: When I updated the drdl, I used tab instead of space, which is causing the mongsqld to error out Fix: Just replace tab with space and everything is back to normal
Read more

MongoDB Tips: Kill long running processes

-
This is just a quick and simple script to find all active opid that has been running over 10 seconds and they are running against the databases and collections you can specify in the "ns" filter. It's best to first run db.currentOp(    {      "active" : true,      "secs_running" : { "$gt" : 10 },      "ns" : {$in:["equipment.detachment","personnel.detail","personnel.unavailability","personnel.detachment"]}    } ).inprog.forEach(function (doc) { print(doc.opid); }) and verify your output before you execute the kill command in my experience to make sure you are killing the processes that are meant to be killed. Once verifed, simply run: db.currentOp(    {      "active" : true,      "secs_running" : { "$gt" : 10 },      "ns" : {$in:["<db1>.<col1>","<db2>.<col2>","<dbn>.<coln>
Read more