..
Category : devops
If you want to see the XML for the entire VM, using: The edited sections will look like this: and To automount this on VM startup, y..
Examp..
..
..
How to renew a domain using DNS: The error: “none of the preferred challenges are supported by the selected plugin” Switch to –manual and switch to use DNS: Edit the domain online, add a T..
Install gitlab runner, docker version: https://docs.gitlab.com/runner/install/docker.html Register the runner: Then edit the config.toml and set priviledged=true and restart the gitlab-runner container Watch the log The resulting runner configuration, and an example config.toml where docker connects v..
W..
This shows you how to create a nexus3 repository, create an HTTP connector (on port 8123), and docker login against that connector, and docker push images to the repo. Create the repo using http and additionally allow port 8123: Select docker(hosted) Since this is running on 8081, we can use http://host.domain:8081 to log in from, locally. 8123 is used for https ..
First, you can set up a mounted share drive from a NAS if you have one. You have to use ID 200 if you do this, because docker runs as 200 Ne..
You’re stuck at this place: http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login Create a service account: Get the secret: Ex output: Copy the token, including the 6 characters after -token (in the above example it’s “cluster-admin-dashboard-sa-token-hhxv9“) Describe the secret to get the token: Example output: Copy the entire token, in this example from “ey… ” to “…t7g” Go to the login ..
Note: if Kubernetes is running on VirtualBox, add the port mapping so that you can access port 8001 from localhost In the shell, instead of running kubectl proxy, run: And then from the other system, hit the login URL: http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/prox..
..
Log into your private registry manually from the shell: then grab this file: # the entire JSON string, and add it in Gitlab under your Group -> Settings -> CI/CD -> Variables, and add new variable:# Key: DOCKER_AUTH_CONFIG# Value: the JSON string from ..
On the registry server, which is on the network over http, accessible over port 5000, you can start it as: or with authentication, you do this instead: (only change myusernamehere and mysecretpasswordhere ) Once you’ve created the registry, leave that server and go to another server and try to log in: On the gateway server, have your ..
..
Set up the subdomain forward, and wait for it to propagate. When you can ping the domain, it’s ready. Be root Edit config file that’s available. nano /etc/nginx/sites-available/server.research.example.com Link it from available to enabled: Create empty dir to serve subdomain: Restart nginx Make sure you can hit the URL over http (https not quite yet) ..
On the build server, the server with Gitlab on it, create the directory where to cache jars: If you don’t have maven, install it: Edit your maven’s settings.xml file: Edit the gitlab-runner’s config.toml file: and the volumes entry, which maps <gitlab server’s directories>: Restart the runner: In the .gitlab-ci.yml file, specify -Dmaven.repo.local=/root/m2 so that the ..