profile

rfswift profile

Manage container profiles — YAML presets for quick container creation.

Synopsis

rfswift profile [subcommand] [options]

Profiles bundle image, network mode, features (desktop, realtime, privileged), device mappings, capabilities, cgroup rules, and port bindings into a single named preset. Instead of typing long rfswift run commands, you can create a profile once and reuse it.

Subcommands

Profile Storage

Profiles are stored as individual YAML files in a platform-specific directory:

~/.config/rfswift/profiles/

~/Library/Application Support/rfswift/profiles/

%APPDATA%\rfswift\profiles\

Each profile is a standalone .yaml file that you can edit, copy, or share.

Profile Format

A profile YAML file contains:

name: sdr-full
description: Full SDR suite with all tools and device support
image: penthertz/rfswift_noble:sdr_full
network: host
desktop: false
desktop_ssl: false
no_x11: false
privileged: false
realtime: true
devices: ""
bindings: ""
exposed_ports: ""
port_bindings: ""
caps: ""
cgroups: ""
vpn: ""

Profile Fields

Examples

Initialize Default Profiles

Generate the built-in starter profiles:

rfswift profile init

This creates 12 default profiles covering common RF/security use cases:

To overwrite existing profiles:

rfswift profile init --force

List Profiles

rfswift profile list

Displays a table with name, description, image, network mode, and enabled features for all profiles.

Show Profile Details

# By name
rfswift profile show sdr-full

# Interactive selection
rfswift profile show

Shows the full configuration and the equivalent rfswift run CLI command.

Create a Profile Interactively

rfswift profile create

Launches a step-by-step wizard to create a new profile:

1. Profile name — unique identifier (e.g., my-sdr-setup)
2. Description — what this profile is for
3. Image selection — pick from local images or enter manually
4. Network mode — host, NAT, bridge, or join existing NAT network
5. Feature toggles — desktop, SSL, no-X11, privileged, realtime
6. Device mappings — optional device paths
7. Volume bindings — optional host:container paths
8. Port mappings — simplified hostPort:containerPort format
9. Capabilities — multi-select from common Linux capabilities (NET_ADMIN, SYS_RAWIO, etc.)
10. Cgroup rules — multi-select from common device access rules (USB, serial, sound, etc.)
11. Recap and confirm

The profile is saved as a YAML file that you can further edit manually.

Delete a Profile

# By name
rfswift profile delete wifi

# Interactive selection
rfswift profile delete

Edit a Profile Manually

Profiles are plain YAML files — edit them with any text editor:

# Linux
nano ~/.config/rfswift/profiles/sdr-full.yaml

# macOS
nano ~/Library/Application\ Support/rfswift/profiles/sdr-full.yaml

Using Profiles with rfswift run

Basic Usage

Use a profile with the --profile flag:

rfswift run --profile sdr-full -n my_sdr

This applies all the profile’s settings (image, network, features, devices, etc.) and creates the container.

Profile + CLI Overrides

CLI flags override profile values, so you can customize on the fly:

# Use wifi profile but with a different image
rfswift run --profile wifi -n my_wifi -i penthertz/rfswift_noble:sdr_full

# Use sdr-full profile but in NAT mode
rfswift run --profile sdr-full -n isolated_sdr -t nat

# Use headless profile but add realtime
rfswift run --profile headless -n headless_rt --realtime

Profile in the Interactive Wizard

When you run rfswift run without -i and -n, the wizard offers profile selection as the first step:

? Start from a profile?
  > No profile (manual configuration)
    sdr-full — Full SDR suite with all tools and device support
    wifi — WiFi pentesting and assessment tools
    pentest-full — Full pentest setup: SDR + desktop + NAT isolation
    ...

After selecting a profile, you’re asked:

? Use profile 'sdr-full' as-is?
  > Yes, use as-is
    No, let me customize

• Yes, use as-is: Skips all configuration steps — only asks for the container name, shows a recap, and creates the container. This is the fastest way to spin up a container.
• No, let me customize: Pre-fills all wizard fields with the profile’s values, then lets you change anything before creation. You can also choose a different image while keeping all other profile settings.

Sharing Profiles

Since profiles are plain YAML files, sharing is straightforward:

# Copy a profile to another machine
scp ~/.config/rfswift/profiles/my-setup.yaml user@remote:~/.config/rfswift/profiles/

# Share a team-wide profile
cp team-standard.yaml ~/.config/rfswift/profiles/

Related Commands

• run - Create containers (supports --profile flag)
• Configurations - Global configuration file
• Running RF Swift - Core workflows and features