coreos / coreos/coreos-assembler
`cosa run` (devshell default) does not connect to SCOS 10
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 393
- Forks
- 193
- Avg merge
- 17h 6m
- Merged PRs (30d)
- 5
Description
Bug Report
I'm working on https://github.com/openshift/os/pull/1498 to be able to test the Ignition gdisk vendoring changes.
With https://github.com/openshift/os/pull/1498, I get a working system that I can run test on with kola, access using cosa run --devshell-console but not with cosa run --devshell.
Environment
What operating system is being used to run coreos-assembler? Fedora Kinoite 40
What operating system is being assembled? SCOS 10
Is coreos-assembler running in Podman or Docker? podman
If Podman, is coreos-assembler running privileged or unprivileged? privileged
Expected Behavior
cosa run works with SCOS 10
Actual Behavior
The command remains stuck on:
[STARTUP] ---
Reproduction Steps
- Build SCOS 10 from https://github.com/openshift/os/pull/1498
cosa run
Other Information
- Setting up a libvirt system and using SSH works
- I can run kola tests against this image
- It works with
--devshell-console
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by building SCOS 10 from the referenced OpenShift pull request and running cosa run with Podman. Compare the default --devshell path with --devshell-console and the SSH/libvirt behavior; done means cosa run connects instead of remaining at [STARTUP] ---.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- operating-systems, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100