fedora-docs-l10n/fedora-coreos/master/pages/tutorial-containers — Chinese (Simplified) (zh_CN) @ Fedora Weblate: [Install] WantedBy=multi-user.target

The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not update the repository.

Zen

Translation

English type: delimited block -

Chinese (Simplified) (zh_CN)

Needs editing

This translation is currently locked.

Skip

	English	Chinese (Simplified) (zh_CN)	Actions
	Setting up SSH access and starting containers at boot
	Complete all the steps described in the xref:tutorial-setup.adoc[initial setup page] before starting this tutorial. Make sure you have create file `ssh-key.pub` following the instructions provided in the https://docs.fedoraproject.org/en-US/fedora-coreos/tutorial-setup/#_ssh_public_key[prerequisites] for the tutorial. We will use this key in the Butane configuration file that we are about to write.
	In this tutorial, we will set up SSH access and start a container at boot. Fedora CoreOS is focused on running applications/services in containers thus we recommend trying to run containers and avoid modifying the host directly. Running containers and keeping a pristine host layer makes automatic updates more reliable and allows for separation of concerns with the Fedora CoreOS team responsible for the OS and end-user operators/sysadmins responsible for the applications.
	As usual, we will set up console autologin, a hostname, systemd pager configuration, but we will also:
	Add an SSH Key for the `core` user from the local `ssh-key.pub` file.
	Add a systemd service (`failure.service`) that fails on boot.
	Add a running container via a Podman https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html[quadlet systemd.unit container file].
	This `etcd-member.container` will then be associated with a `etcd-member.service` on the running system.
	`etcd-member.service` will launch and manage the lifecycle of the container using `podman`.
	Writing the Butane config and converting to Ignition
	Similarly to what we did in the second provisioning scenario, we will write the following Butane config in a file called `containers.bu`:
	Example with automatic serial console login, SSH key, and multiple systemd units
	variant: fcos version: {butane-latest-stable-spec} passwd: users: - name: core ssh_authorized_keys_local: - ssh-key.pub systemd: units: - name: serial-getty@ttyS0.service dropins: - name: autologin-core.conf contents: \| [Service] # Override Execstart in main unit ExecStart= # Add new Execstart with `-` prefix to ignore failure ExecStart=-/usr/sbin/agetty --autologin core --noclear %I $TERM TTYVTDisallocate=no - name: failure.service enabled: true contents: \| [Service] Type=oneshot ExecStart=/usr/bin/false RemainAfterExit=yes
	[Install] WantedBy=multi-user.target storage: files: - path: /etc/hostname mode: 0644 contents: inline: \| tutorial - path: /etc/profile.d/systemd-pager.sh mode: 0644 contents: inline: \| # Tell systemd to not use a pager when printing information export SYSTEMD_PAGER=cat - path: /etc/containers/systemd/etcd-member.container mode: 0644 contents: inline: \| [Unit] Description=Run a single node etcd After=network-online.target Wants=network-online.target
	[Container] ContainerName=etcd Image=quay.io/coreos/etcd:latest Network=host Volume=etcd-data:/etcd-data Exec=/usr/local/bin/etcd \ --name node1 --data-dir /etcd-data \ --initial-advertise-peer-urls http://127.0.0.1:2380 \ --listen-peer-urls http://127.0.0.1:2380 \ --advertise-client-urls http://127.0.0.1:2379 \ --listen-client-urls http://127.0.0.1:2379 \ --initial-cluster node1=http://127.0.0.1:2380
	[Install] WantedBy=multi-user.target
	Run Butane to convert that to an Ignition config:
	butane --pretty --strict --files-dir=./ containers.bu --output containers.ign
	Now let's provision it:
	# Setup the correct SELinux label to allow access to the config chcon --verbose --type svirt_home_t containers.ign
	# Start a Fedora CoreOS virtual machine virt-install --name=fcos --vcpus=2 --ram=2048 --os-variant=fedora-coreos-stable \ --import --network=bridge=virbr0 --graphics=none \ --qemu-commandline="-fw_cfg name=opt/com.coreos/config,file=${PWD}/containers.ign" \ --disk="size=20,backing_store=${PWD}/fedora-coreos.qcow2"
	On the console you will see:
	Fedora CoreOS 38.20230709.3.0 Kernel 6.3.11-200.fc38.x86_64 on an x86_64 (ttyS0)
	SSH host key: SHA256:T5V4oXMZ0UJ7WRGzNiUOkggO7p5yojTVBUxa6N3vIoQ (ECDSA) SSH host key: SHA256:oBAvj2kaKKKK++gnchTbxpp/iphvX6EHr0EynwXZ19c (ED25519) SSH host key: SHA256:Yg2fdA7GC1eoHtIjawDA+WffTKTuNy5ZhQHUJx5GRHk (RSA) enp1s0: 192.168.124.119 fe80::9b5c:330d:2020:1c9e Ignition: ran on 2023/08/03 18:17:45 UTC (this boot) Ignition: user-provided config was applied Ignition: wrote ssh authorized keys file for user: core tutorial login: core (automatic login)
	Fedora CoreOS 38.20230709.3.0 [systemd] Failed Units: 1 failure.service [core@tutorial ~]$
	If you would like to connect via SSH, disconnect from the serial console by pressing `CTRL` + `]` and then use the reported IP address for the NIC from the serial console to log in using the `core` user via SSH:
	$ ssh core@192.168.124.119 The authenticity of host '192.168.124.119 (192.168.124.119)' can't be established. ED25519 key fingerprint is SHA256:oBAvj2kaKKKK++gnchTbxpp/iphvX6EHr0EynwXZ19c. This key is not known by any other names Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added '192.168.124.119' (ED25519) to the list of known hosts. Fedora CoreOS 38.20230709.3.0 Tracker: https://github.com/coreos/fedora-coreos-tracker Discuss: https://discussion.fedoraproject.org/tag/coreos
	Last login: Thu Aug 3 18:18:06 2023 [systemd] Failed Units: 1 failure.service
	The `Failed Units` message is coming from the https://github.com/coreos/console-login-helper-messages[console login helper messages] helpers. This particular helper shows us when `systemd` has services that are in a failed state. In this case we made `failure.service` with `ExecStart=/usr/bin/false`, so we intentionally created a service that will always fail in order to illustrate the helper messages.
	Now that we’re up and don’t have any real failures we can check out the status of `etcd-member.service`, which was generated from our `etcd-member.container` file.
	[core@tutorial ~]$ systemctl status --full etcd-member.service ● etcd-member.service - Run a single node etcd Loaded: loaded (/etc/containers/systemd/etcd-member.container; generated) Drop-In: /usr/lib/systemd/system/service.d └─10-timeout-abort.conf Active: active (running) since Thu 2023-08-03 18:17:57 UTC; 2min 24s ago Main PID: 1553 (conmon) Tasks: 10 (limit: 2238) Memory: 86.5M CPU: 3.129s CGroup: /system.slice/etcd-member.service ├─libpod-payload-31af97b0ef902b3b3b3d717bd98947b209701b9585db2129ca53f4b33962415e │ └─1555 /usr/local/bin/etcd ... └─runtime └─1553 /usr/bin/conmon ...

Loading…

None

String updated in the repository

English

Chinese (Simplified) (zh_CN) 0 characters edited Current translation Empty

a year ago

Browse all string changes

Things to check

Inconsistent

This string has more than one translation in this project or is untranslated in some components.

Reset

Glossary

English	Chinese (Simplified) (zh_CN)
No related strings found in the glossary.

14880911 String information

Source string description

type: delimited block -

Flags

no-wrap, placeholders:r"`[\w.\/\-_=@&*:$●+~()\] ]*`"

Source string location

pages/tutorial-containers.adoc:88

String age

a year ago

Last updated

a year ago

Source string age

a year ago

Translation file

po/zh_CN/master/pages/tutorial-containers.po, string 16

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.