Unable to persist user after installation on Ubuntu 22.04.3 about cubic HOT 9 OPEN

I suspect this is because 22.04 uses Subiquity and overlay file systems, whereas 20.04 did not.
I'll look into this.

from cubic.

The same happened to me. The base image I imported was also ubuntu22.04.3.
When I installed nfs, rcpbind was automatically installed and an _rpc user was created, but the user was not saved on the new host.
By the way, the contents of the /etc/fstab file I modified are not saved either. Is this a similar problem? @PJ-Singh-001

from cubic.

I have a similar situation.
I did install additional packages in the terminal, but after generating iso and installed on the hardware, those packages are not there.
It took changes from the Pressed/user-data thought.

from cubic.

I have a similar situation. I did install additional packages in the terminal, but after generating iso and installed on the hardware, those packages are not there. It took changes from the Pressed/user-data thought.

@misiek303,
Your question regarding packages was answered in Issue #295, Installed packages via apt in Cubic Terminal don't exist in the final ISO.

from cubic.

@prorealize,

I will assume you are customizing Ubuntu Server 22.04 ISO, which uses the Subiquity installer, and not the 22.04 Desktop ISO.

You will need to install using the minimal install option, as described in Issue #295, Installed packages via apt in Cubic Terminal don't exist in the final ISO).

You can create users using the adduser command as described in Issue #3, How to create custom users on the login screen?. I suggest using adduser instead of useradd; you can read about the options the adduser command takes (such as -M to not create a home directory) on the man page.

However, you should not have to manually create this user if you install using the minimal install option I described above.

from cubic.

@ChYUYAO,

Ubuntu Server 22.04 uses the Subiquity installer. You will need to install using the minimal install option, as described in Issue #295, Installed packages via apt in Cubic Terminal don't exist in the final ISO).

The /etc/fstab file is overwritten by the installer, because the installer does its own partitioning.

You can use one these techniques to work around this:

1. Keep a customized version of your fstab file in /usr/local/etc. Then copy /etc/local/fstab to /etc/ using the late-commands command in cloud-init.
2. Using the late-commands command in cloud-init, append the necessary line to /etc/fstab with the command echo "<your fstab line>" | tee --append /etc/fstab.

from cubic.

@ChYUYAO,

Ubuntu Server 22.04 uses the Subiquity installer. You will need to install using the minimal install option, as described in Issue #295, Installed packages via apt in Cubic Terminal don't exist in the final ISO).

The /etc/fstab file is overwritten by the installer, because the installer does its own partitioning.

You can use one these techniques to work around this:

1. Keep a customized version of your fstab file in /usr/local/etc. Then copy /etc/local/fstab to /etc/ using the late-commands command in cloud-init.
2. Using the late-commands command in cloud-init, append the necessary line to /etc/fstab with the command echo "<your fstab line>" | tee --append /etc/fstab.

I've tried the second way, but still haven't customized what I need in /etc/fstab.

late-commands:
- echo "/mnt/var /var none bind" | tee --append /etc/fstab
- echo "/mnt/home /home none bind" | tee --append /etc/fstab
- echo "/mnt/tmp /tmp none bind" | tee --append /etc/fstab

iso:ubuntu-22.04.3-live-server-amd64.iso
mysystem:ubuntu 20.04 desktop

from cubic.

I think the format needs to be something like this:

#cloud-config
autoinstall:
  version: 1
  late-commands:
  - curtin in-target --target=/target -- <your shell command>

Where <your shell command> should be replaced with your shell command.

I suggest making sure the late-commands works by creating a simple test file first to ensure you have the correct format in your couid-init file.

#cloud-config
autoinstall:
  version: 1
  late-commands:
  - curtin in-target --target=/target -- touch /opt/test.txt

from cubic.

@PJ-Singh-001 Hi, I have the similar issue.
I installed docker.io and dnsmasq in the Terminal part. During the installation, user dnsmasq and group docker is created.
When finished the ISO and install a server with this ISO, the user dnsmasq and group docker are missing which cause dnsmasq and docker failed to start.

Would you please help to take a look on this? Thank you in adavnace!

from cubic.