DEV Community: klo2k

Create Ubuntu 24.04.2 VM in Hyper-V, with "Enhanced Session" RDP support (Windows 11, xrdp, development)

klo2k — Fri, 07 Mar 2025 07:16:40 +0000

Create Ubuntu 24.04.2 VM in Hyper-V, with "Enhanced Session" RDP support (Windows 11, xrdp, development)

To setup an Ubuntu 24.04.2 development Hyper-V VM, with built-in "Enhanced Session" + Remote Desktop Protocol (RDP) support (until it's available in Hyper-V's "Quck Create"):

Create Hyper-V VM
Configure VM for "Enhanced Session", allow nested virtualisation
Start VM, install Ubuntu
XRDP Setup
Optional, but really useful setup
Fix Xrdp slow performance
Connect to VM

Create Hyper-V VM

Create VM ("New" > "Virtual Machine"):

# Specify Name and Location
Name: Ubuntu 24.04
[Next]

# Specify Generation
Generation: 2
[Next]

# Assign Memory
Startup memory: 4096
[Next]

# Configure Networking
Connection: Default Switch
[Next]

# Connect Virtual Hard Disk
Create a virtual hard disk:
  Name: Ubuntu 24.04.vhdx
  Size: 256GB
[Next]

# Installation Options
Install an operating system from a from bootable CD/DVD-ROM:
  Image file: ubuntu-24.04.2-desktop-amd64.iso

[Finish]

DO NOT START VM YET

Configure VM (Right-click "Ubuntu 24.04" > "Settings..."):

# Change boot order (boot from HDD before Network)
Firmware
  DVD Drive
  HDD
  Network

# Necessary to boot Ubuntu
Security
  Enable Secure Boot
  Template: Microsoft UEFI Certificate Authority

# Optional
Integration Services
  (Check all)

# Optional
Checkpoints
  (Uncheck) Use automatic checkpoints

# Optional
Automatic Stop Action
  Shut down the guest operating system

[OK]

DO NOT START VM YET

Configure VM for "Enhanced Session", allow nested virtualisation

From admin PowerShell (Right-click "Windows PowerShell" > "Run as administrator..."):

# Connect with Enhanced Session
Set-VM -VMName 'Ubuntu 24.04' -EnhancedSessionTransportType HvSocket

# Allow nested virtualisation (optional)
Set-VMProcessor -VMName 'Ubuntu 24.04' -ExposeVirtualizationExtensions $true
# Verify - expect 'True'
(Get-VMProcessor -VMName 'Ubuntu 24.04').ExposeVirtualizationExtensions

Start VM, install Ubuntu

Start VM, install with default options, using the latest installer (Update installer if promoted).

Note:
1. ❗ Make sure Require my password to log in is checked (this is needed for xrdp)
2. Example Default installation options:
```
  Interactive installation
  Default selection
  Erase disk and install Ubuntu
```
Restart - Hard-reset VM if you get error: SQUASHFS error: Failed to read block

XRDP Setup

Install Xrdp + apply Ubuntu 24.04 specific fixes:

💡 You may find it easier to do this over SSH: apt install -y openssh-server, then ssh to new VM.

# As root
sudo su -

# Hyper-V integration services
apt install -y linux-tools-virtual-hwe-24.04 linux-cloud-tools-virtual-hwe-24.04
# Fix-up journal log error
mkdir /usr/libexec/hypervkvpd/
ln -s /usr/sbin/hv_get_dhcp_info /usr/libexec/hypervkvpd/hv_get_dhcp_info
ln -s /usr/sbin/hv_get_dns_info /usr/libexec/hypervkvpd/hv_get_dns_info

# Install xrdp
apt install -y xrdp
cp -p /etc/xrdp/sesman.ini /etc/xrdp/sesman.ini.original
cp -p /etc/xrdp/xrdp.ini /etc/xrdp/xrdp.ini.original

# Allow enhanced session
sed -i -e 's/^port=3389$/port=3389 vsock:\/\/-1:3389/g' /etc/xrdp/xrdp.ini

# Rename redirected drives to 'shared-drives'
sed -i -e 's/FuseMountName=thinclient_drives/FuseMountName=shared-drives/g' /etc/xrdp/sesman.ini


# Use "Ubuntu" session
cat > /etc/xrdp/startubuntu.sh << EOF
#!/bin/sh
export GNOME_SHELL_SESSION_MODE=ubuntu
export XDG_CURRENT_DESKTOP=ubuntu:GNOME
exec /etc/xrdp/startwm.sh
EOF
chmod a+x /etc/xrdp/startubuntu.sh
# use the script to setup the ubuntu session
sed -i -e 's/startwm/startubuntu/g' /etc/xrdp/sesman.ini

# Fixes login black screen delay
echo "blacklist vmw_vsock_vmci_transport" > /etc/modprobe.d/blacklist-vmw_vsock_vmci_transport.conf

# Unlock keyring on login
cat > /etc/pam.d/xrdp-sesman <<'EOT'
#%PAM-1.0
auth     required  pam_env.so readenv=1
auth     required  pam_env.so readenv=1 envfile=/etc/default/locale
@include common-auth
-auth    optional  pam_gnome_keyring.so
-auth    optional  pam_kwallet5.so

@include common-account

@include common-password

# Ensure resource limits are applied
session    required     pam_limits.so
# Set the loginuid process attribute.
session    required     pam_loginuid.so
# Update wtmp/lastlog
session    optional     pam_lastlog.so quiet
@include common-session
-session optional  pam_gnome_keyring.so auto_start
-session optional  pam_kwallet5.so auto_start
EOT

Optional, but really useful setup

Reduce boot delay:

cp -p /etc/default/grub /etc/default/grub.default
# Show boot log instead of splash screen
sed -i -e 's/GRUB_CMDLINE_LINUX_DEFAULT=.*/GRUB_CMDLINE_LINUX_DEFAULT=""/g' /etc/default/grub
# Faster boot - reduce grub wait for input timeout
echo 'GRUB_RECORDFAIL_TIMEOUT=3' >> /etc/default/grub
update-grub

Enable zram (compressed memory), disable swap file:

apt install -y systemd-zram-generator
cp -p /etc/systemd/zram-generator.conf /etc/systemd/zram-generator.conf.original
cat > /etc/systemd/zram-generator.conf <<'EOT'
[zram0]
zram-size = 12288
compression-algorithm = zstd
EOT
systemctl daemon-reload
systemctl restart systemd-zram-setup@zram0

# Disable swap file
cp -p /etc/fstab /etc/fstab.original
sed -i -e 's@^/swap.img@#/swap.img@g' /etc/fstab
swapoff /swap.img
rm /swap.img

Full reboot (must power off > power on - else Enhanced Session won't kick-in)

poweroff

Fix Xrdp slow performance

In Feb 2025 one of the Ubuntu update caused a performance regression with the Xorg backend (even on 1920x1080...).

To switch to the VNC Backend:

# As root
sudo su -

# Install TigerVNC
apt install -y tigervnc-standalone-server tigervnc-xorg-extension

# Configure tigervnc backend
cp -p /etc/xrdp/sesman.ini /etc/xrdp/sesman.ini.20250213
sed -z -i -e \
's/'\
'\(\[Xvnc\].*\nparam=96\n\)\n\[/'\
'\1param=-CompareFB\nparam=1\nparam=-ZlibLevel\nparam=0\nparam=-geometry\nparam=1920x1080\n\n[/'\
'gi' /etc/xrdp/sesman.ini

# Remove Xorg backend
sed -z -i -e \
's/'\
'\[Xorg\].*\ncode=20\n\n\[/'\
'[/'\
'gi' /etc/xrdp/xrdp.ini

reboot

Connect to VM

Either using mstsc / Hyper-V

Profit 😉

Credits

Building Docker image from stdin/pipe

klo2k — Tue, 28 Feb 2023 06:51:03 +0000

Using - as docker build parameter, you can pipe in any text as your Dockerfile.

I use this trick to quickly test parts of a Dockerfile.

e.g.:

# Build the image, with '-' + heredoc as input
# Works the same with pipe input
docker build --tag klo2k/test - <<'EOT'
FROM ubuntu:latest

# Some complicated looking stuff you wanna try out quickly
RUN <<'EOS' /bin/bash
  echo "${HOSTNAME}" > /tmp/out
EOS

CMD echo "Build: $(cat /tmp/out) Run: ${HOSTNAME}"
EOT

# Run
docker run --rm -it klo2k/test

Example Output:

Build: buildkitsandbox Run: a16cd7dc16ed

Hope you find this useful!

Convert directory into BTRFS subvolume

klo2k — Mon, 27 Feb 2023 07:40:05 +0000

I've been using BTRFS for development and am loving the simplicity and features it provides.

One thing I do a lot is database snapshot on docker volume (to test db migration) - which I can easily do with BTRFS.

Here's how:

Convert docker volume directory into BTRFS subvolume
Snapshot the docker volume (now a BTRFS subvolume)

Convert docker volume directory into BTRFS subvolume

# Directory to convert into BTRFS subvolume
dirPath='/var/lib/docker/test_docker_volume'

# Rename original dierctory
mv "${dirPath}" "${dirPath}_original"

# Create btrfs subvolume
btrfs subvolume create "${dirPath}"

# Copy as "reflink" for speed and save space
cp --archive --one-file-system --reflink=always \
  "${dirPath}_original/." "${dirPath}"

# Remove old directory
rm -rf --one-file-system "${dirPath}_original"

Snapshot the docker volume

Create a read-only snapshot of test_docker_volume docker volume:

btrfs subvolume snapshot -r \
  /var/lib/docker/test_docker_volume \
  /var/lib/docker/test_docker_volume_bak

Run Docker in WSL2 in 5 minutes (via systemd, without Docker Desktop!)

klo2k — Wed, 23 Nov 2022 07:08:35 +0000

Now WSL2 has systemd support, we can run Docker in WSL without Docker desktop!

TL;DR

Ensure /etc/wsl.conf has
```
[boot]
systemd=true
```

Restart WSL

wsl --shutdown
wsl --distribution Ubuntu

Install docker-cli - see my guide
Log back into WSL > Profit 💫

Complete Guide

Ensure WSL is up-to-date:
```
wsl --update
```
(Optional) Install + configure Ubuntu distro (if you haven't already):
```
wsl --install Ubuntu
```

Configure WSL (assuming "Ubuntu" is your distro):

# Open up "Ubuntu"
wsl --distribution Ubuntu

# Enable systemd via /etc/wsl.conf
{
cat <<EOT
[boot]
systemd=true
EOT
} | sudo tee /etc/wsl.conf

exit

Restart WSL:

wsl --shutdown
wsl --distribution Ubuntu

Check systemd is running - You should see 'OK: Systemd is running' message:

systemctl --no-pager status user.slice > /dev/null 2>&1 && echo 'OK: Systemd is running' || echo 'FAIL: Systemd not running'

Install docker-ce (cmds from my post):

# Install Docker
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
echo \
  "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu \
  $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
sudo apt update
sudo apt install -y docker-ce docker-compose-plugin

# Install docker-compose
sudo ln -s /usr/libexec/docker/cli-plugins/docker-compose /usr/bin/docker-compose

# Add yourself to the docker group
sudo usermod -aG docker $USER

# Exit bash - this is important!!!
exit

Re-login (this is important!):
```
wsl --distribution Ubuntu
```
You can now run docker-cli without Docker Desktop 🙂:
```
docker run --rm -it hello-world
```

Connect DBeaver to Snowflake via Okta SSO (flatpak / snap)

klo2k — Mon, 31 Oct 2022 04:36:15 +0000

DBeaver flatpak/snap doesn't allow you to log into Snowflake via browser-based SSO ("externalbrowser"):

The BROWSE action is not supported on the current platform!

If you happen to use Okta, you can use the "Native SSO" feature.

Simply add authenticator driver property, with your Okta instance's URL:
i.e.:

Username (Main tab) would be your Snowflake username (i.e. select current_user();).

Note browser-based SSO works with the .deb installer - but this method has the benefit of not spamming your browser with new tab every time dbeaver needs to re-authenticate.

Fix SSD TRIM on UGREEN UASP USB SATA adapter/enclosure

klo2k — Thu, 22 Sep 2022 17:25:58 +0000

I've finally figured out how to fix SSD TRIM on the newer UGREEN USB SATA adapter and enclosure, both on my machine and Raspberry Pi-s!

We need to:

Set 'unmap' on /sys/block/sda/device/scsi_disk/0:0:0:0/provisioning_mode (the standard fix)
Set '2147450880' on /sys/block/sda/queue/discard_max_bytes

Without the 2nd fix, fstrim would only work on small partitions.

Permanent fix via UDEV Rules

Add these udev rules to /etc/udev/rules.d/99-ugreen-sata-adapter-trim-enable.rules:

# UGREEN SATA USB adapter cable - ASMedia Technology Inc. Ugreen Storage Device
ACTION=="add|change", ATTRS{idVendor}=="174c", ATTRS{idProduct}=="225c", SUBSYSTEM=="scsi_disk", ATTR{provisioning_mode}="unmap"
ACTION=="add|change", ATTRS{idVendor}=="174c", ATTRS{idProduct}=="225c", SUBSYSTEM=="block", ATTR{queue/discard_max_bytes}="2147450880"

# UGREEN SATA Enclosure - ASMedia Technology Inc. ASM1153 SATA 3Gb/s bridge
ACTION=="add|change", ATTRS{idVendor}=="174c", ATTRS{idProduct}=="1153", SUBSYSTEM=="scsi_disk", ATTR{provisioning_mode}="unmap"
ACTION=="add|change", ATTRS{idVendor}=="174c", ATTRS{idProduct}=="1153", SUBSYSTEM=="block", ATTR{queue/discard_max_bytes}="2147450880"

💡: You may need to change idProduct to your own - check lsusb.

e.g. Here're mine:

# `lsusb` output:
...
Bus 002 Device 034: ID 174c:225c ASMedia Technology Inc. Ugreen Storage Device
...
Bus 002 Device 041: ID 174c:1153 ASMedia Technology Inc. ASM1153 SATA 3Gb/s bridge

Where did 2147450880 come from?

It seems fstrim can still fail on large partitions, with the default discard_max_bytes value too big (4294966784) - we need to set it to the maximum the adapter can handle.

2147450880 is this maximum in my case, calculated from 2 attributes from the adapter:

Maximum unmap LBA count (from sg_vpd)
Logical block length (from sg_readcap)

Here's a small snippet to show yours:

sudo su -
apt install sg3-utils

# Device to check
device=sdh
# e.g. lba_count=4194240
lba_count=$(sg_vpd --all /dev/$device|grep 'Maximum unmap LBA count'|grep -Po '(?<=: )(.*)(?=$)')
# e.g. block_length=512
block_length=$(sg_readcap --long /dev/$device|grep 'Logical block length'|grep -Po '(?<=\=)(.*)(?= bytes)')
# e.g. 2147450880
echo $(( $lba_count * $block_length ))

Symptoms addressed by fix

This fix will be relevant to you if you encounter these errors:

# fstrim -v /
fstrim: /: the discard operation is not supported
fstrim: /: FITRIM ioctl failed: Operation not permitted

And in /var/log/syslog / journalctl:

Sep 22 20:16:19 LINUX kernel: sd 7:0:0:0: [sdg] tag#12 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Sep 22 20:16:19 LINUX kernel: sd 7:0:0:0: [sdg] tag#12 Sense Key : Illegal Request [current] 
Sep 22 20:16:19 LINUX kernel: sd 7:0:0:0: [sdg] tag#12 Add. Sense: Invalid field in cdb
Sep 22 20:16:19 LINUX kernel: sd 7:0:0:0: [sdg] tag#12 CDB: Unmap/Read sub-channel 42 00 00 00 00 00 00 00 18 00
Sep 22 20:16:19 LINUX kernel: print_req_error: 6703 callbacks suppressed
Sep 22 20:16:19 LINUX kernel: blk_update_request: critical target error, dev sdg, sector 39667712 op 0x3:(DISCARD) flags 0x4000 phys_seg 1 prio class 0
Sep 22 20:16:19 LINUX kernel: sd 7:0:0:0: [sdg] tag#13 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Sep 22 20:16:19 LINUX kernel: sd 7:0:0:0: [sdg] tag#13 Sense Key : Illegal Request [current] 
Sep 22 20:16:19 LINUX kernel: sd 7:0:0:0: [sdg] tag#13 Add. Sense: Invalid field in cdb
Sep 22 20:16:19 LINUX kernel: sd 7:0:0:0: [sdg] tag#13 CDB: Unmap/Read sub-channel 42 00 00 00 00 00 00 00 18 00
Sep 22 20:16:19 LINUX kernel: blk_update_request: critical target error, dev sdg, sector 48056312 op 0x3:(DISCARD) flags 0x4000 phys_seg 1 prio class 0
Sep 22 20:16:19 LINUX kernel: sd 7:0:0:0: [sdg] tag#14 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Sep 22 20:16:19 LINUX kernel: sd 7:0:0:0: [sdg] tag#14 Sense Key : Illegal Request [current] 
Sep 22 20:16:19 LINUX kernel: sd 7:0:0:0: [sdg] tag#14 Add. Sense: Invalid field in cdb
Sep 22 20:16:19 LINUX kernel: sd 7:0:0:0: [sdg] tag#14 CDB: Unmap/Read sub-channel 42 00 00 00 00 00 00 00 18 00
Sep 22 20:16:19 LINUX kernel: blk_update_request: critical target error, dev sdg, sector 56444912 op 0x3:(DISCARD) flags 0x4000 phys_seg 1 prio class 0
Sep 22 20:16:19 LINUX kernel: blk_update_request: critical target error, dev sdg, sector 89999312 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sep 22 20:16:19 LINUX kernel: sd 7:0:0:0: [sdg] tag#15 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Sep 22 20:16:19 LINUX kernel: sd 7:0:0:0: [sdg] tag#15 Sense Key : Illegal Request [current] 
Sep 22 20:16:19 LINUX kernel: sd 7:0:0:0: [sdg] tag#15 Add. Sense: Invalid field in cdb
Sep 22 20:16:19 LINUX kernel: sd 7:0:0:0: [sdg] tag#15 CDB: Unmap/Read sub-channel 42 00 00 00 00 00 00 00 18 00
Sep 22 20:16:19 LINUX kernel: blk_update_request: critical target error, dev sdg, sector 64833512 op 0x3:(DISCARD) flags 0x4000 phys_seg 1 prio class 0
Sep 22 20:16:19 LINUX kernel: sd 7:0:0:0: [sdg] tag#16 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Sep 22 20:16:19 LINUX kernel: sd 7:0:0:0: [sdg] tag#16 Sense Key : Illegal Request [current] 
Sep 22 20:16:19 LINUX kernel: sd 7:0:0:0: [sdg] tag#16 Add. Sense: Invalid field in cdb
Sep 22 20:16:19 LINUX kernel: sd 7:0:0:0: [sdg] tag#16 CDB: Unmap/Read sub-channel 42 00 00 00 00 00 00 00 18 00
Sep 22 20:16:19 LINUX kernel: blk_update_request: critical target error, dev sdg, sector 73222112 op 0x3:(DISCARD) flags 0x4000 phys_seg 1 prio class 0
Sep 22 20:16:19 LINUX kernel: sd 7:0:0:0: [sdg] tag#17 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Sep 22 20:16:19 LINUX kernel: sd 7:0:0:0: [sdg] tag#17 Sense Key : Illegal Request [current] 
Sep 22 20:16:19 LINUX kernel: sd 7:0:0:0: [sdg] tag#17 Add. Sense: Invalid field in cdb
Sep 22 20:16:19 LINUX kernel: sd 7:0:0:0: [sdg] tag#17 CDB: Unmap/Read sub-channel 42 00 00 00 00 00 00 00 18 00
Sep 22 20:16:19 LINUX kernel: blk_update_request: critical target error, dev sdg, sector 81610712 op 0x3:(DISCARD) flags 0x4000 phys_seg 1 prio class 0
Sep 22 20:16:19 LINUX kernel: BTRFS warning (device sdg3): failed to trim 1 device(s), last error -95

Credit

This is only possible thanks to this post from Jeff Geerling (he's awesome 👍)

Keychron K5 Function Keys + Unstable Bluetooth fix - Ubuntu 22.04

klo2k — Fri, 08 Jul 2022 14:14:03 +0000

If you have problem getting the F1 - F12 (Function) keys to work, and unstable bluetooth connection on your new Keychron K5 keyboard, this will hopefully help you.

Here are the fixes that worked for me on Ubuntu 22.04.

Fixing top row keys as F1 to F12

So you can actually use the function key row as function keys:

Set keyboard to Windows mode (use hardware switch)
Hold Fn + X + L for 4 seconds to switch to "Function" mode

Apply the fix temporarily --> check if it's working:

echo 0 | sudo tee /sys/module/hid_apple/parameters/fnmode

Apply the fix permanently:

echo "options hid_apple fnmode=0" | sudo tee -a /etc/modprobe.d/hid_apple.conf
sudo update-initramfs -u

Reboot (to verify)

Fixing unstable Bluetooth Connection

Before this fix the keyboard would randomly disconnect.

After this fix, not a single glitch the entire workday 😋

Enable fast connect:

Edit /etc/bluetooth/main.conf - uncomment and set these values:
```
FastConnectable = true
ReconnectAttempts=7
ReconnectIntervals=1, 2, 4
```

Disable bluetooth auto suspend

echo "options btusb enable_autosuspend=n" | sudo tee /etc/modprobe.d/btusb_disable_autosuspend.conf
sudo update-initramfs -u

Restart bluetooth

sudo modprobe -r btusb
sudo systemctl restart bluetooth
sudo modprobe btusb

Factory reset keyboard (Hold Fn + Z + J for 4 seconds) --> Re-pair keyboard

This makes no sense but it did seem to make a difference...

Credits

This post is possible thanks to these awesome people:

Install docker, docker-compose in Ubuntu 24.04 in 5 commands

klo2k — Fri, 01 Jul 2022 13:24:15 +0000

Install docker, docker-compose in Ubuntu 24.04 in 5 commands

The official guide takes a bit of reading...

So here's the TL;DR version of it, in 5 commands:

# Install Docker
curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc
chmod 0644 /etc/apt/keyrings/docker.asc
echo \
  "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/ubuntu $(. /etc/os-release && echo "$VERSION_CODENAME") stable" | \
  sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
sudo apt update
sudo apt install -y docker-ce docker-compose-plugin

# Add yourself to 'docker' group
sudo usermod --append --groups docker "${USER}"

# Install docker-compose
sudo ln -s /usr/libexec/docker/cli-plugins/docker-compose /usr/bin/docker-compose

Add yourself to docker group (no need for sudo docker every time)

sudo usermod -aG docker $USER

Profit 😉

Get Git to remember passwords - git credential manager examples

klo2k — Tue, 28 Jun 2022 06:50:02 +0000

Sometimes it's necessary to use password-based authentication via https when using remote repo.

When used in CI/CD pipelines, we need to do this non-interactively, and not expose password in the remote's URL.

To do this, we can use git's own credential manager.

Here are some examples to help us understand and use it.

TL;DR (Full Example)
- Setup
- Add password, pull from repo
- Clean-up
More Examples
- Save credentials
- Get credentials
- Selectively remove credentials

TL;DR (Full Example)

Setup

# Get a shell into git container
docker run --rm -it --entrypoint=/bin/sh alpine/git:v2.34.2

# Store credentials to file
git config --global credential.helper store
# Note: To store in memory (for 1 day)
# git config --global credential.helper 'cache --timeout=86400'

# Clean out existing credentials
rm ~/.git-credentials

# Force non-interactive mode
export GIT_TERMINAL_PROMPT=0

Add password, clone from repo

Add password

git credential approve <<'EOT'
url=https://example.com/jsmith/testrepo.git
username=jsmith
password=abc123
EOT

Clone repo - no password asked / exposed 😉️

git clone https://jsmith@example.com/jsmith/testrepo.git

Clean-up

rm ~/.git-credentials
exit

More Examples

Save credentials

git credential approve <<'EOT'
url=https://example.com
username=user0
password=0000
EOT

git credential approve <<'EOT'
url=https://example.com/test-group/test-repo1.git
username=user1
password=1111
EOT

git credential approve <<'EOT'
url=https://example.com/test-group/test-repo2.git
username=user2
password=2222
EOT

Get credentials

git credential fill <<'EOT'
url=https://example.com/test-group/test-repo1.git
username=user1
EOT

git credential fill <<'EOT'
url=https://example.com/test-group/test-repo2.git
username=user2
EOT

git credential fill <<'EOT'
url=https://example.com
username=user0
EOT

Selectively remove credentials

git credential reject <<'EOT'
url=https://example.com
username=user2
EOT

# Ensure it's removed - expect to error-out with "fatal: could not read Password for 'https://user2@example.com': terminal prompts disabled"
git credential fill <<'EOT'
url=https://example.com/test-group/test-repo2.git
username=user2
EOT