containers/engine-stressor

disk stress - volume options in many distro possible

Open

#6 aperta il 9 ago 2024

Vedi su GitHub
 (2 commenti) (0 reazioni) (0 assegnatari)Shell (3 fork)auto 404
enhancementgood first issuehelp wanted

Metriche repository

Star
 (4 star)
Metriche merge PR
 (Metriche PR in attesa)

Descrizione

Run all volume/store options possible against podman versus main distro available, like Fedora, CentOS Stream, Ubuntu etc.

A good start is use the disk stress test already available.

Why? We noticed some random read only filesystem issue appearing when deploying containers via podman on CentOS Stream 9:

Writing manifest to image destination
INFO: List of current containers: (0)
INFO: No memory usage data returned for memory_eater_base_container. Continuing to sleep.
9f31cc878efe4a15f0f7403372997a56ed025c4dcaf2066dfdf27bc4a7527179
INFO: Waiting for the container to be fully started...
INFO: Container memory_eater_base_container is running.
INFO: Installing dependencies in the container
INFO: List of current containers: (1) memory_eater_base_container
INFO: Current memory usage of memory_eater_base_container: 1.15%
Config error: [Errno 30] Read-only file system: '/var/log/dnf.log': '/var/log/dnf.log'
INFO: Cloning the engine-stressor repository
/bin/sh: line 1: git: command not found

Guida contributor