journald | journald support for slog-rs

I was able to resolve this, unfortunately I won't be able to find out why this happened.

I tried removing and installing docker-ce and dependencies again. I wasn't able to remove due to containerd.service not stopping. I found it was set to always restart, which would normally make sense. I then ran sudo systemctl disable docker containerd and rebooted. I confirmed those services were no longer running by following journalctl output, looking for the usual restarting and core-dump errors from docker and containerd.

I ran sudo apt remove docker-ce and sudo apt autoremove again, then ran docker's get-docker.sh which reinstalled docker. I then ran sudo systemctl enable docker containerd and sudo systemctl start docker containerd. Docker is the same version it was before and the hello-world container and other containers of mine that wasn't previously running is now running successfully.

You have to also implement Clone() from the zapcore.Encoder interface. If you wish to keep the parent logger unaltered, you have to construct an actual clone — possibly with the same config, so you might want to store it as a field:

You can use a custom encoder that embeds a zapcore.Encoder.

Embedding the encoder gives you the implementation of all methods "for free" with the same configuration you have now. Then you can implement only EncodeEntry with the additional logic you require.

NOTE: You still have to implement Clone() if you plan to use structured logging, e.g. logger.With(). More info: Why custom encoding is lost after calling logger.With in Uber Zap?

Back to your main question, this is a working example; see the comments in code for additional explanation:

slogger2 (and it's predecessor slogger) provide a low-latency in-memory log system. slogger2 is closer conceptually to the Linux kernel log service (eg. slog2f() is approximately equivalent to printk()), but runs as a user-space daemon independent of the kernel as QNX uses a microkernel architecture.

Like the Linux kernel log, slogger2 does not write messages to disk by itself; if you want to store messages in a file, you are required to run another process to manage that (ie. slog2info is analogous to klogd). It is possible to route syslog into slogger2, to have a single source of message traffic; it is also possible to route slogger2 to syslog, to leverage syslogd's better tools for writing files to disk.

As mentioned by @ErikSjölund there has been an active treat on https://github.com/containers/podman. Apparantely Centos (Podman Machine) does not (yet) support different types of volume creation on the machine.

It's not perse Podman lacking this feature it's waiting for CentOS to support this feature as well.

However, should you want to mount a local directory onto the machine I recommend have a look at https://github.com/containers/podman/issues/8016#issuecomment-995242552. It describes how to do a read-only mount on CoreOS (or break compatibility with local version).

Info:

https://github.com/containers/podman/pull/11454 https://github.com/containers/podman/pull/12584

The COPY step will create the file with the uid/gid of 0:0 (root:root) within the / directory where normal users have no access. And the selected base image is configured to run as uid 1001. Probably the easiest is to switch back to root temporarily to run that step.

Nuking /var/lib/docker seems to get the system working again - this removes all images and lots of other docker-related data.

This doesn't feel like a great solution, but it'll have to do for now.

I would answer "How can I install curl and bash at build-time" not "How to set time in Docker container at build time":

I guess apk is failing because repo TLS certificate dl-cdn.alpinelinux.org is not valid after 2037 = valid TLS connection can be created. You only need to install package, so you may sacrifice TLS security in this case and plain HTTP connectuon to repository can be used as a workaround. E.g.