alpine auth.err getty[3453]: tcgetattr: I/O error^M
- Lenguaje dominante
- Go
- Estrellas
- 30.8k
- Forks
- 613
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
### Describe the Bug
A clear and concise description of what the bug is.
`/var/log/messages` is spammed with:
```
May 21 13:17:20 alpine auth.err getty[3453]: tcgetattr: I/O error^M
May 21 13:17:30 alpine daemon.info init: process '/sbin/getty -L 0 ttyS0 vt100' (pid 3453) exited. Scheduling for restart.
May 21 13:17:31 alpine daemon.info init: starting pid 3454, tty '/dev/ttyS0': '/sbin/getty -L 0 ttyS0 vt100'
```
Every 10s or so.
### Version
#### Colima Version:
```
colima version development
git commit: unknown
runtime: docker
arch: aarch64
client: v20.10.14
server: v20.10.11
```
What is the output of `colima version`
#### Lima Version:
```
limactl version 0.10.0
```
What is the output of `limactl --version`
#### Qemu Version
What is the output of `qemu-img --version`
```
qemu-img version 7.0.0
Copyright (c) 2003-2022 Fabrice Bellard and the QEMU Project developers
```
### Operating System
- [ ] macOS Intel
- [x] macOS m1
- [ ] Linux
### To Reproduce
Steps to reproduce the behavior:
1. `colima start`
2. `colima ssh -- sudo tail -f /var/log/messages`
### Expected behavior
A clear and concise description of what you expected to happen.
### Additional context
Add any other context about the problem here.
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Línea de trabajo
The issue is about a serial console getty error in an Alpine Linux VM managed by Colima. Start by examining the VM configuration in the Colima codebase, likely under the lima VM setup. Look for how ttyS0 is configured and why getty fails with an I/O error. Check the logs via 'colima ssh -- sudo tail -f /var/log/messages' to see the pattern. Understanding Linux serial console setup and the interaction with QEMU is needed.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- go, linux, shell
- Área
- cli, operating-systems
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100