AlmaLinux / AlmaLinux/bootc-images

[BUG]: Using 9.4 with podman-bootc error

Abierto
#16 3 comentarios 0 reacciones 0 asignados Ver en GitHub
bug
Lenguaje dominante
Dockerfile
Estrellas
50
Forks
16
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Current Behavior

I've built an Alma 9.4 as a base image and when I try to login to it with `podman-bootc ssh ` if fails with
```
Connecting to vm 17de7fa355360b3df260d73e8f1e6eeb78f39021128ec60cf5d69336d79b6ed8. To close connection, use `~.` or `exit`
root@localhost: Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).
```
`podman-bootc list` shows that the image is running successfully so I am assuming there is some configuration missing.
```
ID REPO SIZE CREATED RUNNING SSH PORT
17de7fa35536 myimage:latest 10.7GB 51 minutes ago true 46651
```
fedora base images seem to run ok with this flow.

### Expected Behavior

Should be able to login to running image with podman-bootc or have instructions on how to enable it.

### Steps To Reproduce

With Version 9.4 Create a bootc image
publish to a registry
run `podman-bootc run --filesystem xfs imagename`
You should be dropped into a shell on the running machine.

### Anything else?

_No response_

### Search terms

podman-bootc ssh

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.