Wait. Wait. This sounds like a trap! Protection money?
Uncategorized
-
Bot Detection. Powered by a (friendly) bot
-
Falling asleep while reading my own blog
Probably I´ll go back to books soon.
-
Paper shows strong evidence ….
… of the presence of intelligence in three-day-old coffee. Nguyen et al., 2025 (preprint)
-
Someone At YouTube Needs Glasses
-
Deal with Dotfiles
-
Dieser Skill wird im Zeitalter von KI wichtiger denn je
Lesen!
-
Install Gitlab Runner in Docker Rootless for dind
Gitlab offers a well designed platform for open source projects. In the free version it is possible to use up to 400 min (?) runner time for CI-Jobs. It is also possible to connect self hosted gitlab-runners to power up you CI-Environment.
In my self administered environments I use a docker rootless setup most of the time.
How to register a gitlab-runner from within a docker-rootless environment?
1. Go to your group or project. Find the „runners“ entry in the „Build“ menu.
2. Add a new runner and copy the token to an editor or leave the page open for further reference (see step 7). Save everything.
3. SSH to your docker rootless host as „docker“ user.
4. Find your userid by typing
id– Lets say it gives 1004
5. Start a gitlab-runner container using a socket mount from your users directory
/run/user/1004docker run -d --name gitlab-runner --restart always -v /run/user/1004/docker.sock:/var/run/docker.sock -v gitlab-runner-config:/etc/gitlab-runner gitlab/gitlab-runner:latest
6. Register the runner
docker run --rm -t -i -v /srv/gitlab-runner/config:/etc/gitlab-runner --name gitlab-runner gitlab/gitlab-runner register
7. If you are on gitlab.com simply add
https://gitlab.comas runner location. It will find your runner by entering the token you have copied in Step 2. User
dockeras executer.8. Now the runner should be connected. You can make use of by configuring it at your
project/settings/ciconfig.9. You can also add additional runner config under
~/.local/share/docker/volumes/gitlab-runner-config/_data/config.tomlGNU nano 6.2 /home/docker/.local/share/docker/volumes/gitlab-runner-config/_data/config.toml concurrent = 1 check_interval = 0 shutdown_timeout = 0 [session_server] session_timeout = 1800 [[runners]] name = "my-runner" url = "https://gitlab.com/" id = 47413623 token = "XXX-your-token-here-XXX" token_obtained_at = 2025-05-12T06:29:10Z token_expires_at = 0001-01-01T00:00:00Z executor = "docker" [runners.cache] MaxUploadedArchiveSize = 0 [runners.cache.s3] [runners.cache.gcs] [runners.cache.azure] [runners.docker] tls_verify = false image = "docker:latest" privileged = false disable_entrypoint_overwrite = false oom_kill_disable = false disable_cache = false volumes = ["/cache",,"/run/user/$ID_OF_YOUR_DOCKER_USER/docker.sock:/var/run/docker.sock"] shm_size = 0 network_mtu = 010. Docker Compose
docker-compose.ymlservices: gitlab-runner: image: gitlab/gitlab-runner:latest restart: always container_name: gitlab-runner volumes: - gitlab-runner-config:/etc/gitlab-runner - /run/user/1004/docker.sock:/var/run/docker.sock volumes: gitlab-runner-config: -
Müssen Plattformen wie Facebook auch proaktiv Inhalte löschen?
Müssen Plattformen wie Facebook, TikTok, Instagram, YouTube und Co. ab Kenntnis illegaler Inhalte auch proaktiv nach sinngleichen Inhalten suchen und diese sodann ohne weiteren Hinweis ebenfalls löschen? Darüber wird ab dem 18.2.2025 der Bundesgerichtshof entscheiden.
-
Bash shortcuts