action #153499
Updated by okurz 4 months ago
## Motivation
Based on reports by users, e.g. in https://matrix.to/#/!dRljORKAiNJcGEDbYA:opensuse.org/$LbL5oeNDTwzikKhlZdH39GOSkR2qZ7Nvoie6Yvx1Khs developer mode might not work straight out of the box in the container setup:
> dbrouwer @Sam Thursfield i'm curious if you got developer mode working in a container? Yesterday adamw pointed out that we had the same problem experimenting with running openqa remotely in containers. I eventually had to comment out the logic in makeWsUrlAbsolute() that expects the port to be 80 or 443 since I wanted to run a rootless container and was pushing port 80 to 8081. Curious if you did the same or if you found another way around it?
## Acceptance criteria
* **AC1:** The openQA developer Developer mode in openQA live run is ensured to work based on automatic installation or documentation in the common container setup of openQA
## Suggestions
* Try out a container deployment yourself because it's so easy
* Check if the developer mode works or how to get it work. For this read http://open.qa/docs/#debugdevelmode work
* Ensure our tests cover that. Likely openQA-in-openQA tests are helpful here
* Implement what is missing. Consider configurable ports and port deltas, see https://github.com/os-autoinst/openQA/pull/5435 missing
* Where needed extend documentation
* As necessary research about https://docs.podman.io/en/latest/markdown/podman-port.1.html or similar to find out what ports containers expose
Back