84f0b017d9
This fixes a large swath of compatibility issues, for the same reasons as overlayfs makes a lot of things Just Work. The ugly part of course is doing hidden copyups inside the filesystem. We've gone quite a long time with the "pure rofiles" mode, and have made changes to various bits of userspace to be compatible with it. But what finally made me give up on that is glibc's locale-archive; there's a patch for it that is stalled, but even if it was applied we would still need to work with older glibc. This issue comes to the fore in unified core 🌐 mode, as without this we won't get a correct locale archive. Closes: #1171 Approved by: jlebon |
||
|---|---|---|
| .. | ||
| check | ||
| common | ||
| compose-tests | ||
| composedata | ||
| ex-container-tests | ||
| gpghome | ||
| manual | ||
| utils | ||
| vmcheck | ||
| compose | ||
| ex-container | ||
| README.md | ||
Tests are divided into three groups:
-
Tests in the
checkdirectory are non-destructive and uninstalled. Some of the tests require root privileges. Usemake checkto run these. -
The
composechecktests currently require uid 0 capabilities - the default in Docker, or you can run them via a user namespace. They are non-destructive, but are installed.To use them, you might do a
make && sudo make installinside a Docker container.Then invoke
./tests/compose. Alternatively of course, you can simply run the tests on a host system or in an existing container, without doing a build.Note: This is intentionally not a
Makefiletarget because it doesn't require building and doesn't use uninstalled binaries. -
Tests in the
vmcheckdirectory are oriented around using Vagrant. Usemake vmcheckto run them. See alsoHACKING.mdin the top directory.
The common directory contains files used by multiple
tests. The utils directory contains helper utilities
required to run the tests.