$ cargo build --release
Compiling krunkit v0.1.0 (/Users/walters/src/github/containers/krunkit)
error: linking with `cc` failed: exit status: 1
|
= note: env -u IPHONEOS_DEPLOYMENT_TARGET -u TVOS_DEPLOYMENT_TARGET LC_ALL="C" PATH="/Users/walters/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/bin:/usr/bin:/bin:/opt/podman/bin:/opt/homebrew/bin:/Users/walters/.cargo/bin:/usr/local/bin" VSLANG="1033" ZERO_AR_DATE="1" "cc" "-arch" "arm64" "/var/folders/9j/jpms114j76q64fhjrq8kw71w0000gn/T/rustcAo9YET/symbols.o" "/Users/walters/src/github/containers/krunkit/target/release/deps/krunkit-0fa2d8ec3a3c8061.krunkit.65e17eeac52f16f7-cgu.00.rcgu.o" "/Users/walters/src/github/containers/krunkit/target/release/deps/krunkit-0fa2d8ec3a3c8061.krunkit.65e17eeac52f16f7-cgu.01.rcgu.o" "/Users/walters/src/github/containers/krunkit/target/release/deps/krunkit-0fa2d8ec3a3c8061.krunkit.65e17eeac52f16f7-cgu.02.rcgu.o" "/Users/walters/src/github/containers/krunkit/target/release/deps/krunkit-
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
podman --log-level debug machine init --now 01/02/24 10:13:12 AM | |
INFO[0000] /Users/walters/src/github/containers/podman/bin/darwin/podman filtering at log level debug | |
DEBU[0000] Using Podman machine with `applehv` virtualization provider | |
DEBU[0000] Detected compression format gzip | |
Extracting compressed file: podman-machine-default_fedora-coreos-39.20231204.2.1-applehv.aarch64.raw: done | |
DEBU[0007] creating runtimeDir: /var/folders/9j/jpms114j76q64fhjrq8kw71w0000gn/T/podman | |
DEBU[0007] resizing disk to 100 GiB | |
DEBU[0007] resizing /Users/walters/.local/share/containers/podman/machine/applehv/podman-machine-default_fedora-coreos-39.20231204.2.1-applehv.aarch64.raw to 107374182400 bytes | |
Machine init complete | |
Starting machine "podman-machine-default" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
apiVersion: v1 | |
kind: ConfigMap | |
metadata: | |
name: test-unit | |
annotations: | |
bootc.prefix: "/usr/lib/systemd/system" | |
data: | |
example.service: | | |
[Service] | |
ExecStart=echo hello world |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
/* | |
$ gcc -O2 $(pkg-config --cflags --libs openssl glib-2.0) -Wall -o sha256-bench-openssl sha256-bench-openssl.c | |
$ ./sha256-bench-openssl | |
openssl: 3900 msec | |
glib: 7950 msec | |
speedup: 2.04 | |
$ | |
*/ | |
#define _GNU_SOURCE 1 |
Feb 27 15:07:10 cosa-devsh podman[1491]: 2023-02-27 15:07:10.972716987 +0000 UTC m=+0.192006555 container create 0260f6a600eb61b4cf3f1b536c60b13954309da06197188251e0ff1482543434 (image=docker.io/library/busybox:latest, name=loving_driscoll)
Feb 27 15:07:10 cosa-devsh kernel: bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
Feb 27 15:07:10 cosa-devsh NetworkManager[1169]: <info> [1677510430.9996] manager: (cni-podman0): new Bridge device (/org/freedesktop/NetworkManager/Devices/3)
Feb 27 15:07:11 cosa-devsh podman[1491]: 2023-02-27 15:07:10.917733235 +0000 UTC m=+0.137022821 image pull busybox
Feb 27 15:07:11 cosa-devsh NetworkManager[1169]: <info> [1677510431.0286] manager: (veth7c04525f): new Veth device (/org/freedesktop/NetworkManager/Devices/4)
Feb 27 15:07:11 cosa-devsh kernel: cni-podman0: port 1(veth7c04525f) entered blocking state
Feb 27 15:07:11 cosa-devsh kernel: cni-podman0: port 1(veth7c04525f) entered disab
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
``` | |
-rw-r--r--. 1 walters walters 613M Feb 15 17:16 qcow2.xz | |
-rw-r--r--. 1 walters walters 669M Feb 15 17:58 qcow2.zstd | |
$ time xz -d < qcow2.xz >/dev/null | |
________________________________________________________ | |
Executed in 12.62 secs fish external | |
usr time 12.51 secs 190.00 micros 12.51 secs | |
sys time 0.09 secs 69.00 micros 0.09 secs |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
!/bin/sh | |
# Clone a copy-on-write "gold" cloud image, resize it to the target, and | |
# use virt-install to create a VM, attaching a cloud-init metadata ISO. | |
# Run in /var/lib/libvirt/images | |
img=$1 | |
shift | |
name=$1 | |
shift | |
size=$1 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#![feature(try_trait_v2)] | |
use anyhow::Result; // 1.0.57 | |
use core::ops::Try; | |
trait TryOrElse<T> { | |
fn try_or_else<R: Try<Output = T>, F: FnOnce() -> R>(self, f: F) -> R; | |
} | |
// Proposed new API for Option https://github.com/rust-lang/libs-team/issues/59 |
In Rust, the Option and Result types are really common. Here are a few idioms I've discovered for working with them using combinators which can simplify code:
// Our program needs a string for something (e.g. filename, database table name, etc).
// To start, we can get this as an optional string - here a CLI argument, but it could be anything; e.g.
// a value parsed from JSON, etc. The `.nth(1)` call here gives us an `Option<String>`.
// We want to compute a fallback value, but doing so can fail (e.g. return `Result<String>`).
If you're seeing this linked because you used an internal-to-RH proprietary realtime chat system,
please consider instead interacting on an asynchronous, public channel such as a GitHub issue,
Bugzilla (but uncheck the "Private bug" bits), or public mailing list like fedora-devel@
or centos-devel
. Another good alternative is https://discussion.fedoraproject.org/
You'll see it said that Red Hat is an enterprise software company with a FOSS development model.
NewerOlder