Stuart Shelton
Stuart Shelton
I have an account which receives duplicate messages (with differing Message-IDs) a few minutes apart from various mailing-lists. It would be helpful to have an option to exclude the `Date:`...
Running from a container-image with podman: ``` + podman run --privileged --rm --volume /boot:/boot:ro --volume /dev/cpu:/dev/cpu:ro --volume /lib/modules:/lib/modules:ro spectre-meltdown-checker --update-fwdb Spectre and Meltdown mitigation detection tool v0.45 Fetching MCE.db from...
Running from a container-image with `podman`: ``` + podman run --privileged --rm --volume /boot:/boot:ro --volume /dev/cpu:/dev/cpu:ro --volume /lib/modules:/lib/modules:ro spectre-meltdown-checker --kernel /boot/kernel-5.18.12-gentoo --config /boot/config-5.18.12-gentoo --map /boot/System.map-5.18.12-gentoo -v -v Spectre and Meltdown...
Prior to v2.11, RPi-Monitor displayed defined items in a single-column format. Now, the default is a multi-column display... although in my case, the two items I care about most happen...
A `RUN` directive including the following (entirely legitimate, AFAIK) command invocation: ```bash sed -i \ "/^apphome=/ s|\"[^\"]*\"$|\"${APPHOME}\"|" \ "${APPHOME}/runapp.sh" ``` ... generates the following output: ``` TypeError: Cannot read property...
... it'd be awesome if a Preferences option was added to allow selection of icon location, such as Top Left, Top, Top Right, Left, Centre (Default), Right, Bottom Left, Bottom,...
The `Multipass` (v1.0.0) application fails to launch from macOS 10.15.1 desktop: ``` $ export QT_DEBUG_PLUGINS=1 $ /Applications/Multipass.app/Contents/MacOS/Multipass QFactoryLoader::QFactoryLoader() checking directory path "/Library/Application Support/com.canonical.multipass/bin/multipass.gui.app/Contents/MacOS/platforms" ... qt.qpa.plugin: Could not find the Qt...
When a `RUN` block contains a pipeline, not having set `pipefail` results in: ``` /ER0001/ Set the SHELL option -o(-eo for Alpine image) pipefail before RUN with a pipe in...
Now that `busybox` is a recognised shell dialect, it would be useful to be able to optionally configure (via command-line options and/or `.shellcheckrc`?) `#!/bin/sh` shebang lines encountered in analysed scripts...
I've been looking for ways to ascertain the high-water-mark memory usage for a running container, and one suggestion given was `runc events --stats `. `crun` doesn't currently seem to implement...