Using an answerfile with setup-alpine - Revision history

PlumpPot: Fix typo

2026-03-27T20:46:49Z

Fix typo

← Older revision		Revision as of 20:46, 27 March 2026
Line 162:		Line 162:

	* [[Alpine_setup_scripts#setup-disk\|<code>setup-disk</code>]]		* [[Alpine_setup_scripts#setup-disk\|<code>setup-disk</code>]]
	:: DISKOPTS="''~~etup~~-disk options''"		:: DISKOPTS="''setup-disk options''"
	::: Specify setup-disk options:		::: Specify setup-disk options:
	::: {{Cat\|setup-disk -h\|<nowiki>		::: {{Cat\|setup-disk -h\|<nowiki>

John3-16: Amended introduction regarding a fully non-interactive setup, discouraged for general use.

2025-12-06T01:38:11Z

Amended introduction regarding a fully non-interactive setup, discouraged for general use.

← Older revision		Revision as of 01:38, 6 December 2025
Line 1:		Line 1:
	To perform ~~a non-interactive~~ Alpine Linux [[Installation]], ~~answerfiles~~ can be created and used to preprogram various answers to the questions prompted by the [[Alpine_configuration_management_scripts#setup-alpine\|setup-alpine]] script. [[Alpine_configuration_management_scripts#Environment_Variables\|Environment variables]] can be added to configure the behavior of any given utility called by the script.		To perform an Alpine Linux [[Installation\|installation]] that approaches being fully non-interactive, an answerfile can be created and used to preprogram various answers to the questions prompted by the [[Alpine_configuration_management_scripts#setup-alpine\|setup-alpine]] script. [[Alpine_configuration_management_scripts#Environment_Variables\|Environment variables]] can be added to configure the behavior of any given utility called by the script.

			A fully non-interactive {{ic\|setup-alpine}} installation would entail replacing the prompt for a root password with an empty password, and suppressing the verification prompt to erase the target disk. This could only be achieved if {{ic\|setup-alpine}} were run by combining both facilities above – i.e. an answerfile and a certain environment variable considered below – plus an additional {{ic\|setup-alpine}} switch for an empty password. These prompts serve as safety and security guards, and their suppression would '''not be recommended''' in general use.

	== Creating an initial answerfile ==		== Creating an initial answerfile ==

Jvvv: Change the '-c' to '-f', as '-c' creates the answerfile and has no effect with ERASE_DISKS. The point is that ERASE_DISKS is an environment variable and won't be added to the answerfile with the '-c' (create) option.

2025-12-05T19:37:53Z

Change the '-c' to '-f', as '-c' creates the answerfile and has no effect with ERASE_DISKS. The point is that ERASE_DISKS is an environment variable and won't be added to the answerfile with the '-c' (create) option.

← Older revision		Revision as of 19:37, 5 December 2025
Line 228:		Line 228:

	'''Fully non-interactive''' {{ic\|setup-disk}}: The {{ic\|setup-disk}} section still prompts to confirm whether to erase your target stated in the answerfile. To avoid this, [[Alpine_configuration_management_scripts#Environment_Variables\|'''use the following with caution''']], as it is bound to '''''immediately erase the target media''''':		'''Fully non-interactive''' {{ic\|setup-disk}}: The {{ic\|setup-disk}} section still prompts to confirm whether to erase your target stated in the answerfile. To avoid this, [[Alpine_configuration_management_scripts#Environment_Variables\|'''use the following with caution''']], as it is bound to '''''immediately erase the target media''''':
	{{Cmd\|<nowiki>ERASE_DISKS=</nowiki><var>/path/to/targetmedia</var> setup-alpine -c <var>/path/to/answerfile</var>}}		{{Cmd\|<nowiki>ERASE_DISKS=</nowiki><var>/path/to/targetmedia</var> setup-alpine -f <var>/path/to/answerfile</var>}}

	It is not necessary to use an answerfile to get the same functionality.		It is not necessary to use an answerfile to get the same functionality.

John3-16: "fully-non-interactive setup-disk" reduced, amended and moved to /#Environment_variables_and_setup-alpine/, using ERASE_DISKS as a command-line environment variable instead, elaborated in Alpine_configuration_management_scripts#Environment_Variables.

2025-11-29T18:14:55Z

**"fully-non-interactive setup-disk"** reduced, amended and moved to #Environment_variables_and_setup-alpine: , using ERASE_DISKS as a command-line environment variable instead, elaborated in Alpine_configuration_management_scripts#Environment_Variables.

← Older revision		Revision as of 18:14, 29 November 2025
Line 214:		Line 214:
	::: ROOT_SIZE="50%VG"		::: ROOT_SIZE="50%VG"
	::		::
	::'''Fully non-interactive {{ic\|setup-disk}}:''' {{ic\|setup-disk}} prompts which is the target install media, so for a [https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10549 fully non-interactive] {{ic\|setup-disk}} process when the answerfile is used, identify what the installation path for your target disk will be, and then add the following ''export variable'' line into your answerfile where, say, {{Path\|/dev/mmcblk0}} is the target and ''sys'' is the mode:

	~~::<code>export ERASE_DISKS=<var>/dev/mmcblk0</var> setup-disk -m sys <var>/dev/mmcblk0</var></code>~~

	~~::The first instance of {{Path\|/dev/mmcblk0}} declares that it is safe to erase that disk without prompting while the second marks the path for partitioning, formatting, and installation.~~
	::Remember that the path very possibly may change after a reconfiguration, say, if a media is removed or moved after reboot. For safety, in ''all cases'', ensure that the target media path is correctly identified, as '''''an incorrect path is bound to cause an unintended erasure of media'''''. Consider consulting {{ic\|fdisk -l}} beforehand on the media that will run the {{ic\|setup-alpine}}) instruction, for example.

	* [[Alpine_setup_scripts#setup-lbu\|<code>setup-lbu</code>]]		* [[Alpine_setup_scripts#setup-lbu\|<code>setup-lbu</code>]]
	:: LBUOPTS="<em>MEDIA</em>"		:: LBUOPTS="<em>MEDIA</em>"
Line 231:		Line 224:
	== Environment variables and setup-alpine ==		== Environment variables and setup-alpine ==

	~~It is not necessary to use an answerfile to get the same functionality.~~ Another way to achieve the same		Another way to achieve the same
	thing is to set these variables in the environment, either exported or on the commandline.		thing is to set these variables in the environment, either exported or on the commandline.

			'''Fully non-interactive''' {{ic\|setup-disk}}: The {{ic\|setup-disk}} section still prompts to confirm whether to erase your target stated in the answerfile. To avoid this, [[Alpine_configuration_management_scripts#Environment_Variables\|'''use the following with caution''']], as it is bound to '''''immediately erase the target media''''':
			{{Cmd\|<nowiki>ERASE_DISKS=</nowiki><var>/path/to/targetmedia</var> setup-alpine -c <var>/path/to/answerfile</var>}}

			It is not necessary to use an answerfile to get the same functionality.
	{{Cmd\|DISKOPTS{{=}}<q>-e -L -m sys /dev/sda</q> ROOT_SIZE{{=}}<q>50&percnt;VG</q> setup-alpine}}		{{Cmd\|DISKOPTS{{=}}<q>-e -L -m sys /dev/sda</q> ROOT_SIZE{{=}}<q>50&percnt;VG</q> setup-alpine}}
	The above command specifies to do a system disk install with lvm on encrypted partition, and that the root		The above command specifies to do a system disk install with lvm on encrypted partition, and that the root

Prabuanand: rephrased word

2025-11-29T15:07:40Z

rephrased word

← Older revision		Revision as of 15:07, 29 November 2025
Line 1:		Line 1:
	To perform ~~unattended~~ Alpine Linux [[Installation]], answerfiles can be created and used to preprogram various answers to the questions prompted by the [[Alpine_configuration_management_scripts#setup-alpine\|setup-alpine]] script. [[Alpine_configuration_management_scripts#Environment_Variables\|Environment variables]] can be added to configure the behavior of any given utility called by the script.		To perform a non-interactive Alpine Linux [[Installation]], answerfiles can be created and used to preprogram various answers to the questions prompted by the [[Alpine_configuration_management_scripts#setup-alpine\|setup-alpine]] script. [[Alpine_configuration_management_scripts#Environment_Variables\|Environment variables]] can be added to configure the behavior of any given utility called by the script.

	== Creating an initial answerfile ==		== Creating an initial answerfile ==

Prabuanand: added category, Introduction and see also section, wikilinks

2025-11-29T15:03:55Z

added category, Introduction and see also section, wikilinks

← Older revision		Revision as of 15:03, 29 November 2025
Line 1:		Line 1:
			To perform unattended Alpine Linux [[Installation]], answerfiles can be created and used to preprogram various answers to the questions prompted by the [[Alpine_configuration_management_scripts#setup-alpine\|setup-alpine]] script. [[Alpine_configuration_management_scripts#Environment_Variables\|Environment variables]] can be added to configure the behavior of any given utility called by the script.

	== Creating an initial answerfile ==		== Creating an initial answerfile ==

	To get an quick start with setup-alpine answerfiles, a starter answerfile can be generated with:		To get an quick start with setup-alpine answerfiles, a starter answerfile can be generated with:
	{{Cmd\|setup-alpine -c <var>PATH_TO_FILENAME</var>}}		{{Cmd\|setup-alpine -c <var>PATH_TO_FILENAME</var>}}
Line 227:		Line 230:

	== Environment variables and setup-alpine ==		== Environment variables and setup-alpine ==

	It is not necessary to use an answerfile to get the same functionality. Another way to achieve the same		It is not necessary to use an answerfile to get the same functionality. Another way to achieve the same
	thing is to set these variables in the environment, either exported or on the commandline.		thing is to set these variables in the environment, either exported or on the commandline.
Line 234:		Line 238:

	This method is probably not realistic for setting many variables, but for using just a few may be justified.		This method is probably not realistic for setting many variables, but for using just a few may be justified.

			== See also ==

			* [[Alpine configuration management scripts#Environment Variables\|Environment Variables]]
			* [[Installation]]

			[[Category:Installation]]

John3-16: /* Answerfile Variables */ Added guidance for a fully-non-interactive setup-disk: "export ERASE_DISKS". See https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10549

2025-11-28T18:55:38Z

Answerfile Variables: Added guidance for a fully-non-interactive setup-disk: "export ERASE_DISKS". See https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10549

← Older revision		Revision as of 18:55, 28 November 2025
Line 210:		Line 210:
	::: If lvm is used, SWAP_SIZE and ROOT_SIZE may specified as percentage of volume group, for example:		::: If lvm is used, SWAP_SIZE and ROOT_SIZE may specified as percentage of volume group, for example:
	::: ROOT_SIZE="50%VG"		::: ROOT_SIZE="50%VG"
			::
			::'''Fully non-interactive {{ic\|setup-disk}}:''' {{ic\|setup-disk}} prompts which is the target install media, so for a [https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10549 fully non-interactive] {{ic\|setup-disk}} process when the answerfile is used, identify what the installation path for your target disk will be, and then add the following ''export variable'' line into your answerfile where, say, {{Path\|/dev/mmcblk0}} is the target and ''sys'' is the mode:

			::<code>export ERASE_DISKS=<var>/dev/mmcblk0</var> setup-disk -m sys <var>/dev/mmcblk0</var></code>

			::The first instance of {{Path\|/dev/mmcblk0}} declares that it is safe to erase that disk without prompting while the second marks the path for partitioning, formatting, and installation.
			::Remember that the path very possibly may change after a reconfiguration, say, if a media is removed or moved after reboot. For safety, in ''all cases'', ensure that the target media path is correctly identified, as '''''an incorrect path is bound to cause an unintended erasure of media'''''. Consider consulting {{ic\|fdisk -l}} beforehand on the media that will run the {{ic\|setup-alpine}}) instruction, for example.

	* [[Alpine_setup_scripts#setup-lbu\|<code>setup-lbu</code>]]		* [[Alpine_setup_scripts#setup-lbu\|<code>setup-lbu</code>]]

John3-16: Added syntax illustration for APKREPOSOPTS to add community repo in addition to CDN repo: "-1 -c"

2025-10-02T01:40:11Z

Added syntax illustration for APKREPOSOPTS to add community repo in addition to CDN repo: "-1 -c"

← Older revision		Revision as of 01:40, 2 October 2025
Line 37:		Line 37:
	PROXYOPTS=none		PROXYOPTS=none

	# Add first mirror (CDN)		# Add first mirror (CDN) - Option -1
	APKREPOSOPTS="-1"		# Enable the community repo - Option -c
			APKREPOSOPTS="-1 -c"

	# Create admin user		# Create admin user

Jvvv at 07:17, 29 June 2025

2025-06-29T07:17:31Z

← Older revision		Revision as of 07:17, 29 June 2025
Line 222:		Line 222:
	thing is to set these variables in the environment, either exported or on the commandline.		thing is to set these variables in the environment, either exported or on the commandline.
	{{Cmd\|DISKOPTS{{=}}<q>-e -L -m sys /dev/sda</q> ROOT_SIZE{{=}}<q>50&percnt;VG</q> setup-alpine}}		{{Cmd\|DISKOPTS{{=}}<q>-e -L -m sys /dev/sda</q> ROOT_SIZE{{=}}<q>50&percnt;VG</q> setup-alpine}}
			The above command specifies to do a system disk install with lvm on encrypted partition, and that the root
			logical volume should be 50% of the volume group.

	This method is probably not realistic for setting many variables, but for using just a few may be justified.		This method is probably not realistic for setting many variables, but for using just a few may be justified.

Jvvv at 04:19, 29 June 2025

2025-06-29T04:19:23Z

← Older revision		Revision as of 04:19, 29 June 2025
Line 1:		Line 1:
	~~{{Tip\|This page is a work in progress. It is currently being actively editted. I will remove this tip before the end of day.}}~~		== Creating an initial answerfile ==

	== ~~Using An Answerfile with setup-alpine~~ ==
	To get an quick start with setup-alpine answerfiles, a starter answerfile can be generated with:		To get an quick start with setup-alpine answerfiles, a starter answerfile can be generated with:
	{{Cmd\|setup-alpine -c <var>PATH_TO_FILENAME</var>}}		{{Cmd\|setup-alpine -c <var>PATH_TO_FILENAME</var>}}