Zen

Translation

[Service]
ExecStartPre=mkdir -p /var/lib/etcd
ExecStartPre=-/bin/podman kill etcd
ExecStartPre=-/bin/podman rm etcd
ExecStartPre=-/bin/podman pull [Container]
ContainerName=etcd
Image=quay.io/coreos/etcd:latest
ExecStart=/bin/podman run --name etcd --net Network=host \
--volume /var/lib/etcdVolume=etcd-data:/etcd-data:z \

 quay.io/coreos/etcd:latest Exec=/usr/local/bin/etcd \
 \
 --name node1 --data-dir /etcd-data --name node1 \
--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
ExecStop=/bin/podman stop etcd
English type: delimited block -
[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
930/6230 · 623

Sign in to save the translation.

English Portuguese (Brazil) Actions
Setting up SSH access and starting containers at boot
Configurando um acesso SSH com contêineres que rodam na inicialização
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.
Nesse tutorial, nós configuraremos acesso SSH e um contêiner que roda na inicialização. Fedora CoreOS é focado em rodar aplicações/serviços em contêineres e recomendamos que tentes rodar contêineres e evites mudar o host diretamente. Rodando contêineres e mantendo uma camada de boa condição no host faz atualizações automáticas serem mais confiáveis e permite a separação de preocupações com a equipe do Fedora CoreOS responsável pelo SO e pelos usuários finais operadores/administradores de sistemas responsáveis pelas aplicações.
As usual, we will set up console autologin, a hostname, systemd pager configuration, but we will also:
Habitualmente, iremos configurar um autologin no console, um hostname, uma configuração de paginador para o systemd e subir o nível de logging do kernel, mas nós também iremos:
Add an SSH Key for the `core` user from the local `ssh-key.pub` file.
Adicione uma chave SSH para o usuário `core`.
Add a systemd service (`failure.service`) that fails on boot.
Adiciona um serviço do systemd (`failure.service`) que falha no 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
Escrevendo a configuração Fedora CoreOS e convertendo para Ignition
Similarly to what we did in the second provisioning scenario, we will write the following Butane config in a file called `containers.bu`:
Similarmente com o que fizemos no segundo cenário de provisionamento, nós vamos escrever a seguinte configuração do Fedora CoreOS em um arquivo chamado `fcct-containers.yaml`:
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
variant: fcos
version: 1.3.0
passwd:
users:
- name: core
ssh_authorized_keys:
- ssh-rsa AAAA...
systemd:
units:
- name: serial-getty@ttyS0.service
dropins:
- name: autologin-core.conf
contents: |
[Service]
# Sobrescreve ExecStart na unidade principal
ExecStart=
# Adiciona um novo ExecStart com o prefixo `-` para ignorar falhas
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
[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: |
# Faz com que o systemd não utilize um paginador ao imprimir informação
export SYSTEMD_PAGER=cat
- path: /etc/sysctl.d/20-silence-audit.conf
mode: 0644
contents:
inline: |
# Aumenta o nível de logging de DEBUG (7) para WARNING (4)
# para esconder mensagens feitas para auditar no console interativo
kernel.printk=4
[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
[Service]
ExecStartPre=mkdir -p /var/lib/etcd
ExecStartPre=-/bin/podman kill etcd
ExecStartPre=-/bin/podman rm etcd
ExecStartPre=-/bin/podman pull quay.io/coreos/etcd
ExecStart=/bin/podman run --name etcd --net=host \
--volume /var/lib/etcd:/etcd-data:z \
quay.io/coreos/etcd:latest /usr/local/bin/etcd \
--data-dir /etcd-data --name node1 \
--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
ExecStop=/bin/podman stop etcd
[Install]
WantedBy=multi-user.target
 
Run Butane to convert that to an Ignition config:
Rode `fcct` para converter isso em uma configuração ignition:
butane --pretty --strict --files-dir=./ containers.bu --output containers.ign
fcct --pretty --strict fcct-containers.yaml --output containers.ign
Now let's provision it:
Agora vamos provisionar isso:
# Setup the correct SELinux label to allow access to the config
chcon --verbose --type svirt_home_t containers.ign
# Configura o rótulo correto do SELinux para permitir acesso à configuração
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
# Inicia uma máquina virtual do Fedora CoreOS
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:
No console serial você verá:
Fedora CoreOS 38.20230709.3.0
Kernel 6.3.11-200.fc38.x86_64 on an x86_64 (ttyS0)
Fedora CoreOS 32.20200715.3.0
Kernel 5.7.8-200.fc32.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)
SSH host key: SHA256:rLJvpsONtyYXW4QCTdHD3Vvn56ERq1AbakWxwRImH2g (ECDSA)
SSH host key: SHA256:/UUqh9nMlFf+2wFSjTMtyLemF6qVEuMHbAh1Td8nJeE (ED25519)
SSH host key: SHA256:ZoKsIc9NZVRLe8ao9uPvc1vsbHa6StdSVMvF6rGWhAI (RSA)
ens2: 192.168.122.142 fe80::5054:ff:fec1:a01f
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 ~]$
[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:
Se você gostaria de se conectar via SSH, desconecte-se do console serial pressionando `CTRL` + `]` e então use o endereço IP reportado para `ens2` pelo serial console para logar usando o usuário `core` 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
ssh core@192.168.122.142
The authenticity of host '192.168.122.142 (192.168.122.142)' can't be established.
ECDSA key fingerprint is SHA256:rLJvpsONtyYXW4QCTdHD3Vvn56ERq1AbakWxwRImH2g.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '192.168.122.142' (ECDSA) to the list of known hosts.
Fedora CoreOS 32.20200715.3.0
Tracker: https://github.com/coreos/fedora-coreos-tracker
Discuss: https://discussion.fedoraproject.org/c/server/coreos/
Last login: Thu Aug 3 18:18:06 2023
[systemd]
Failed Units: 1
failure.service
Last login: Fri Aug 7 10:10:45 2020
[systemd]
Failed Units: 1
failure.service
[core@tutorial ~]$
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.
A mensagem `Filed Units` vem do suport https://github.com/coreos/console-login-helper-messages[mensagens de suporte para login no console]. Esse suporte particular nos mostra quando o `systemd` possui serviços que estão em um estado de falha. Nesse caso nós fazemos `failure.service` com `ExecStart=/usr/bin/false`, então nós intencionalmente criamos um serviço que sempre falhará, no objetivo de ilustrar as mensagens de suporte.
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.
Agora que estamos prontos e não temos falhas reais, nós podemos checar o serviço que nos importa (`etcd-member.service`):

Loading…

User avatar None

String updated in the repository
[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
[Service]
ExecStartPre=mkdir -p /var/lib/etcd
ExecStartPre=-/bin/podman kill etcd
ExecStartPre=-/bin/podman rm etcd
ExecStartPre=-/bin/podman pull quay.io/coreos/etcd
ExecStart=/bin/podman run --name etcd --net=host \
--volume /var/lib/etcd:/etcd-data:z \
quay.io/coreos/etcd:latest /usr/local/bin/etcd \
--data-dir /etcd-data --name node1 \
--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
ExecStop=/bin/podman stop etcd
a year ago
User avatar None

Source string changed
[Service]
ExecStartPre=mkdir -p /var/lib/etcd
ExecStartPre=-/bin/podman kill etcd
ExecStartPre=-/bin/podman rm etcd
ExecStartPre=-/bin/podman pull [Container]
ContainerName=etcd
Image=quay.io/coreos/etcd:latest
ExecStart=/bin/podman run --name etcd --net Network=host \
--volume /var/lib/etcdVolume=etcd-data:/etcd-data:z \

 quay.io/coreos/etcd:latest Exec=/usr/local/bin/etcd \
 \
 --name node1 --data-dir /etcd-data --name node1 \
--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
ExecStop=/bin/podman stop etcd
a year ago
Browse all string changes

Things to check

Starting spaces

Source and translation do not both start with same number of spaces

Fix string

Reset

Mismatching line breaks

Number of new lines in translation does not match source

Reset

Glossary

English Portuguese (Brazil)
container contêiner fedora-docs-l10n/fedora-coreos

String information

Source string description
type: delimited block -
Flags
no-wrap, placeholders:r"`[\w.\/\-_=@&*:$●+~()\] ]*`"
Source string location
pages/tutorial-containers.adoc:85
String age
a year ago
Last updated
a year ago
Source string age
a year ago
Translation file
po/pt_BR/master/pages/tutorial-containers.po, string 15