Explore >> Select a destination
|
You are here 
|
ebourgess.dev | ||
| | | | |
www.fosslicious.com
|
|
| | | | | ||
| | | | |
nickjanetakis.com
|
|
| | | | | Most of the time we connect to Docker running on our local machine, but you can also connect to Docker on a different machine too. | |
| | | | |
blogops.mixinet.net
|
|
| | | | | When I configured forgejo-actions I used a docker-compose.yaml file to execute the runner and a dind container configured to run using privileged mode to be able to build images with it; as mentioned on my post about my setup, the use of the privileged mode is not a big issue for my use case, but reduces the overall security of the installation. On a work chat the other day someone mentioned that the GitLab documentation about using kaniko says it is no longer maintained (see the kaniko issue #3348) so we should look into alternatives for kubernetes clusters. I never liked kaniko too much, but it works without privileged mode and does not need a daemon, which is a good reason to use it, but if it is deprecated it makes sense to look into alternatives, and today I looked into some of them to use with my forgejo-actions setup. I was going to try buildah and podman but it seems that they need to adjust things on the systems running them: When I tried to use buildah inside a docker container in Ubuntu I found the problems described on the buildah issue #1901 so I moved on.Reading the podman documentation I saw that I need to export the fuse device to run it inside a container and, as I found other option, I also skipped it. | |
| | | | |
blog.hackeriet.no
|
|
| | | Let us go over the stack we use to power this blog and why it's both easy to use and fast for our visitors. The goal is to serve the blog as fast as possibl... | ||
