runc | CLI tool for spawning and running containers | Continuous Deployment library

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 probably have "type": "module" in your package.json file. If you remove that it will fix this.

Alternatively, if you want to keep your "type": "module" you could convert your jest.config.js to be jest.config.json (and/or if you have a babel.config.js you will need to convert that one to be babel.config.json as well). Note that you will actually have to convert it to be in JSON format (so, remove module.exports = from it, etc).

This example project goes way more in depth on all this

So I've managed to fix my own issue. I had a thought, and so I did this by removing docker compose v2 (yaml v3) with

To solve "invalid or corrupted package (PGP signature)" error in Arch Linux, we need to update the archlinux-keyring package.

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.

A podman login to a private registry as the root user records the authentication under /run/containers/0/auth.json by default. It will write to ${XDG_RUNTIME_DIR}/containers/auth.json if the variable is set. Verify that the /run/containers path exists, is a directory and you have permission to write to it from within the container. Then do the same for ${XDG_RUNTIME_DIR}/containers if it exists.

My guess is a bind mount of a file on somewhere in one of the paths above is putting a file where podman is expecting a directory to be. This is preventing the application from writing out the auth.json file under that path.

You can also explicitly override the auth file path using export REGISTRY_AUTH_FILE=. Test a login after setting this to a known writable value.

The error message means that Redis is still loading data, i.e. in your case, the AOF file. You cannot run FLUSHALL until the loading finishes.

If you don't need the data to be loaded, you can delete the AOF file before starting Redis.

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.

The error say it all: