Loki is a log-aggregator from the grafana team, aimed to run very cost effective. As an elastic stack feels a bit oversized for my side-projects, i just tested Loki on docker swarm.
log collector: docker-driver vs promtail Loki comes with a log shipper called promtail. But as the docs stated, promtail is not that easy to run with docker (for example, log docker logs to a syslog server and point promtail to syslog), so they built a docker logging plugin....
since an update to fedora32, docker is not able to resolve hostnames. So it is not possible to install new packages or go get something.
tl;dr this is a temporary workaround until an official docker build for fedora is released
docker build --network=host . docker run --network=host imageid and for security reasons, of course for local development only, as this flag opens the whole network to the image (ignoring explicit port mappings too)...
Picking up go is a lot of fun! So does a few of my colleagues :-)
Tobi M. (“the destroyer”) asked if i have a solution to run a golang docker image with the go-sqlite3 driver
I remembered to had the same problem, so after my post about really small docker images, lets add a few more bytes!
the solution This solution is not my own, i found and tried other solutions but stayed with this Dockerfile on github...
building docker images with go should be super easy - picking a minimal image (in my case I build from alpine), build the binary, ADD to the image, run…
the problem your app is not starting, instead you see something like this
standard_init_linux.go:195: exec user process caused "no such file or directory" cause: several modules are calling C code via cgo, and cgo depends on libc. Go found libc on the system it was build on, so it linked to it....
Long, long time ago, i started to manage my spare time projects with git, to make life a bit easier there were tools like gitosis and later gitolite - you managed repositories and public keys in plain text files and git hooks on the server. Last year i decided to join the shiny new world of modern self-hosting git services. I choose Gitea - copied it on the server, started one 40 mb binary, and it was just working - and it was fast....