Reid Priedhorsky

See vasi/squashfuse#66.

See also vasi/squashfuse#70.

So looking over all the issues tagged `doc`, there are a lot of specific critiques and then this one, which basically says “do a revision pass on the documentation to...

@qwofford, what do you think of this proposal? Alternate names include *deform*, *edit*, and *mutate*. It would be nice not to implement the save prompt, i.e., only have the behavior...

> if we somehow stored a series of Dockerfile commands that represents the build cache too This is a cool idea. I can think of a couple approaches: 1. Horrible,...

Regarding exit codes, I analyzed all man pages in §1 and §8 on [man7.org](https://man7.org/linux/man-pages/) to find codes that were rarely used by other software (e.g., code 0 is documented by...

In general this seems like a reasonable approach to me. A few comments: 1. I think there might be two separate issues being conflated here. One is that Charliecloud generated...

Hi, thanks for the report! I don't know much about SELinux either but can you answer a couple questions to get us started: 1. What is your SELinux configuration? 2....

> The "libx32" errors persist. These are harmless, fortunately; see issue #732.

Turns out we already have a feature request to get the digest (#1365), so I'm changing the scope of this issue to just the manifest.