![]() I really hope you guys can help me out here. Has there been any reported cases where the registration token just changed by itself?.How do I just update the registration token without having to unregister a GitLab Runner?.I saw the command docker run -restart=always but I’m not sure if that does what I think it does.How do I make sure that the docker service is always running even after the server restarts (I’m assuming our server rebooted that’s why docker wasn’t running from the first error)?.In the end, I have a few questions so that stuff like this never happens again. I need to update the registration token that was registered on our GitLab Runner - but from the documentation, it seems like I have to unregister the existing one and register another. I’m looking at a few documentations and I can’t find what I’m looking for. Install the docker package: > sudo zypper install docker To automatically start the Docker service at boot time: > sudo systemctl enable rvice In the. You can use both of these options together as long as you don’t specify the same option both as a flag and in the JSON file. This is the preferred option, since it keeps all configurations in a single place. So I was investigating this one and it turns out that the registration token has apparently changed without us having to manually reset it? There are two ways to configure the Docker daemon: Use a JSON configuration file. Jan 10 14:36:52 minikube systemd1: rvice: Failed with result exit-code. Jan 10 14:36:52 minikube systemd1: rvice: Start request repeated too quickly. Remote: You are not allowed to download code from this project.įatal: unable to access ‘ The requested URL returned error: 403 Jan 10 14:36:52 minikube systemd1: Failed to start Docker Application Container Engine. However our CI/CD still doesn’t work - I now get this error: I was able to fix this by running sudo systemctl start docker. roothostname systemctl status docker rvice - Docker Application Container Engine Loaded: loaded (/usr/lib/systemd/system/rvice enabled vendor preset: disabled) Active: failed (Result: start-limit) since Wed 07:39:05 EST 3min 34s ago Docs: Main PID: 7590 (codeexited, status1/FA. Is the docker daemon running? (executor_docker.go:968:0s) I just came back from a few days of vacation and apparently our CI/CD has not been working (it used to work pretty well).ĮRROR: Preparation failed: Cannot connect to the Docker daemon at unix:///var/run/docker.sock.
0 Comments
Leave a Reply. |