Clock skew reported by Meson
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- infrastructure
Research direction
The report reproduces the issue with podman build --runtime krun --network private -f Containerfile-test . while pip builds pycairo under Meson; no libkrun source file or test is named. Start by tracing the krun runtime's build and clock behavior, then reproduce using the provided Containerfile on Fedora. Done means the build completes without Meson's future-timestamp clock-skew error.
Written by the indexing model from the issue text.
Description
I encounter a clock skew error in a Podman build environment when using krun as a runtime. It manifests after pip calls Meson to build pycario.
ERROR: Clock skew detected. File /tmp/pip-install-hd168gdo/pycairo_33684b1947e44aeaa696f3854ba6488a/.mesonpy-xefmlk4i/meson-private/coredata.dat has a time stamp 0.2527s in the future.
I can reliably reproduce this by running podman build --runtime krun --network private -f Containerfile-test ..
Containerfile-test:
FROM registry.fedoraproject.org/fedora-minimal
RUN dnf install -y python-devel gcc pip \
cairo-devel cairo-gobject-devel
RUN pip install --no-cache-dir pycairo
The host is a QEMU (GNOME Boxes) guest running Fedora 44 Workstation.
- Dominant language
- Rust
- Stars
- 2.8k
- Forks
- 279
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 28
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from libkrun/libkrun
-
virtio-fs (Linux passthrough): debug log in do_lookup panics the fs worker on non-UTF-8 file namesPossibly taken @zcl-g5 claimed this 1 day ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
libkrun/libkrun#895 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 2 days
-
All virtiofs shares return ECONNREFUSED in the guest (macOS host, libkrun 1.19.6 + krunkit 1.3.2)Open
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 2 days
Similar issues
-
good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
NuSkooler/enigma-bbs#907 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
bug pixi-build-r
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
prefix-dev/pixi#7229 ·
Maintainers usually reply within 1 day