fdo-mirrors/NetworkManager
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git synced 2025-12-25 22:20:08 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
NetworkManager/tools/nm-guest-data
History
Íñigo Huguet 0ec71289ed tools: nm-in-vm: fix motd 
Message of the day was shown twice because the same bashrc.my file than
for containers was used. That file contained some code to show motd in
the container, where it is not shown by default. But in the VM, the motd
is shown by default, so it was shown twice.

Move the code to show motd to a file used only by nm-in-container and
not by nm-in-vm.

Also, modify the explanation about using prepare-for-system.sh because
it's only valid for Fedora but nm-in-vm can be used with other SOs too.
2023-09-21 15:53:03 +02:00
..
.gitignore tools: nm-in-container: move data to a common path for nm-in-vm 2023-09-21 15:53:03 +02:00
bin-_nm-in-container-setup.sh.in tools: nm-in-container: don't generate files from the script 2023-09-21 15:53:03 +02:00
bin-nm-deploy.sh.in tools: nm-in-container: don't generate files from the script 2023-09-21 15:53:03 +02:00
bin-nm-env-prepare.sh.in tools: nm-in-container: don't generate files from the script 2023-09-21 15:53:03 +02:00
etc-bashrc-motd.my.in tools: nm-in-vm: fix motd 2023-09-21 15:53:03 +02:00
etc-bashrc.my.in tools: nm-in-vm: fix motd 2023-09-21 15:53:03 +02:00
etc-motd-container.in tools: nm-in-container: don't generate files from the script 2023-09-21 15:53:03 +02:00
etc-motd-vm.in tools: nm-in-vm: fix motd 2023-09-21 15:53:03 +02:00
etc-rc.local.in tools: nm-in-container: don't generate files from the script 2023-09-21 15:53:03 +02:00
home-bash_history.in tools: nm-in-container: don't generate files from the script 2023-09-21 15:53:03 +02:00
home-behaverc.in tools: nm-in-container: don't generate files from the script 2023-09-21 15:53:03 +02:00
home-gdb_history.in tools: nm-in-container: don't generate files from the script 2023-09-21 15:53:03 +02:00
home-gdbinit.in tools: nm-in-container: don't generate files from the script 2023-09-21 15:53:03 +02:00
nm-90-my.conf.in tools: nm-in-vm: fix connectivity with host 2023-09-21 15:53:03 +02:00
nm-95-user.conf.in tools: nm-in-container: don't generate files from the script 2023-09-21 15:53:03 +02:00
README.md tools: nm-in-container: move data to a common path for nm-in-vm 2023-09-21 15:53:03 +02:00
systemd-10-host-net.link.in tools: nm-in-vm: fix connectivity with host 2023-09-21 15:53:03 +02:00
systemd-20-nm.override.in tools: nm-in-container: don't generate files from the script 2023-09-21 15:53:03 +02:00
systemd-dhcp-host.service.in tools: nm-in-vm: Debian/Ubuntu with extra pkgs and fixed installation 2023-09-21 15:53:03 +02:00

README.md

Run NetworkManager in Container for Development

Run nm-in-container script for running NetworkManager in a non-root, privileged podman container. Run nm-in-vm to do it in a vitual machine. This is useful for testing NetworkManager for development.

Try ./nm-in-container --help or ./nm-in-vm --help to see options. Inside the container, see the bash history for useful commands and read the hints in "/etc/motd".