Summary:
Subiquity can feed curtin a sources.list template and curtin will do the
right thing. config for that is 'apt/config/sources_list' which then
will then have rendered '$MIRROR', and '$RELEASE' https://git.launchpad.net/curtin/tree/examples/apt-source.yaml#n93
More info:
Curtin is working as designed here, and replacing the ubuntu mirrors
it finds in the /etc/apt/sources.list with the requested mirrors. Other
than that, it does not change the content.
You can see in the provided curtin.log:
No custom template provided, fall back to modifymirrors in /etc/apt/sources.list on the target system
To see what curtin got *in*, I make an educated guess that the 'filesystem.squashfs' image contains the relevant /etc/apt/sources.list.
If you're wondering why curtin updates the existing sources.list, that
is to avoid having to know what the right content is. See bug 1513529
or bug 1177432 for examples of why we are not interested in knowing the
right content and maintaining that knowledge.
What I suggest is to have the images built with the correct data,
Then it will all "just work".
Summary: sources_ list' which then /git.launchpad. net/curtin/ tree/examples/ apt-source. yaml#n93
Subiquity can feed curtin a sources.list template and curtin will do the
right thing. config for that is 'apt/config/
will then have rendered '$MIRROR', and '$RELEASE'
https:/
More info: sources. list with the requested mirrors. Other
Curtin is working as designed here, and replacing the ubuntu mirrors
it finds in the /etc/apt/
than that, it does not change the content.
You can see in the provided curtin.log: sources. list on the target system
No custom template provided, fall back to modifymirrors in /etc/apt/
To see what curtin got *in*, I make an educated guess that the 'filesystem. squashfs' image contains the relevant /etc/apt/ sources. list.
$ iso=ubuntu- 18.04-live- server- amd64.iso filesystem. squashfs > fs.squashfs sources. list root/etc/ apt/sources. list archive. ubuntu. com/ubuntu/ bionic main security. ubuntu. com/ubuntu/ bionic-security main archive. ubuntu. com/ubuntu/ bionic-updates main
$ isoinfo -i "$iso" -J -R -x /casper/
$ unsquashfs -dest squashfs-root/ fs.squashfs /etc/apt/
$ cat squashfs-
deb http://
deb http://
deb http://
That differs from a ubuntu server squash image.
$ wget http:// cloud-images. ubuntu. com/daily/ server/ bionic/ current/ bionic- server- cloudimg- amd64.squashfs squashfs- root/ \
bionic- server- cloudimg- amd64.squashfs /etc/apt/ sources. list squashfs- root/etc/ apt/sources. list squashfs- root/etc/ apt/sources. list squashfs- root/etc/ apt/sources. list
$ unsquashfs -dest server-
$ wc -l server-
49 server-
$ grep -v "^#" server-
$ pastebinit server- squashfs- root/etc/ apt/sources. list paste.ubuntu. com/p/nQvtTksHR s/
http://
$ grep -v "^#" server- squashfs- root/etc/ apt/sources. list | grep . archive. ubuntu. com/ubuntu/ bionic main restricted archive. ubuntu. com/ubuntu/ bionic-updates main restricted archive. ubuntu. com/ubuntu/ bionic universe archive. ubuntu. com/ubuntu/ bionic-updates universe archive. ubuntu. com/ubuntu/ bionic multiverse archive. ubuntu. com/ubuntu/ bionic-updates multiverse archive. ubuntu. com/ubuntu/ bionic-backports main restricted universe multiverse security. ubuntu. com/ubuntu/ bionic-security main restricted security. ubuntu. com/ubuntu/ bionic-security universe security. ubuntu. com/ubuntu/ bionic-security multiverse
deb http://
deb http://
deb http://
deb http://
deb http://
deb http://
deb http://
deb http://
deb http://
deb http://
If you're wondering why curtin updates the existing sources.list, that
is to avoid having to know what the right content is. See bug 1513529
or bug 1177432 for examples of why we are not interested in knowing the
right content and maintaining that knowledge.
What I suggest is to have the images built with the correct data,
Then it will all "just work".