Project

General

Profile

Actions

action #127139

closed

Docs for containerized setup lead to errors and ambiguity

Added by livdywan over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Feature requests
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Observation

Following Container based setup I'm seeing errors with both containers:

podman run --rm -it registry.opensuse.org/devel/openqa/containers15.4/openqa_webui:latest
Trying to pull registry.opensuse.org/devel/openqa/containers15.4/openqa_webui:latest...
Getting image source signatures
Copying blob f4da41d99bf4 done
Copying blob 97034f373f82 done
Copying config 3784f61d4e done
Writing manifest to image destination
Storing signatures
AH00526: Syntax error on line 18 of /etc/apache2/vhosts.d/openqa-ssl.conf:
SSLCertificateFile: file '/etc/apache2/ssl.crt/server.crt' does not exist or is empty

podman run --rm -it registry.opensuse.org/devel/openqa/containers15.4/openqa_worker:latest
Trying to pull registry.opensuse.org/devel/openqa/containers15.4/openqa_worker:latest...
Getting image source signatures
Copying blob dd758c45353Copying blob dd758c453531 [=================>--------------------] 106.6MiB / 221
Copying blob dd758c453531 done
Copying blob 97034f373f82 skipped: already exists
Copying config 3b46535c09 done
Writing manifest to image destination
Storing signatures
^[[<0;48;42M^[[<0;48;42mWarning: /dev/kvm doesn't exist. If you want to use KVM, run the container with --device=/dev/kvm
/run_openqa_worker.sh: line 32:     9 Terminated              qemu-system-x86_64 -S
[info] [pid:12] worker 1:
 - config file:                      not found
 - name used to register:            658021e3eca7
 - worker address (WORKER_HOSTNAME): localhost
 - isotovideo version:               38
 - websocket API version:            1
 - web UI hosts:                     localhost
 - class:                            ?
 - no cleanup:                       no
 - pool directory:                   /var/lib/openqa/pool/1
[error] [pid:12] Errors occurred when reading config file:
 - Config file not found at '/etc/openqa/workers.ini'.
API key and secret are needed for the worker connecting localhost
 at /usr/share/openqa/script/../lib/OpenQA/Worker/WebUIConnection.pm line 50.
    OpenQA::Worker::WebUIConnection::new("OpenQA::Worker::WebUIConnection", "localhost", HASH(0xaaaaee874108)) called at /usr/share/openqa/script/../lib/OpenQA/Worker.pm line 252
    OpenQA::Worker::init(OpenQA::Worker=HASH(0xaaaaf1d4afe8)) called at /usr/share/openqa/script/../lib/OpenQA/Worker.pm line 363
    OpenQA::Worker::exec(OpenQA::Worker=HASH(0xaaaaf1d4afe8)) called at /usr/share/openqa/script/worker line 125

There is a suggestion to follow Containerized setup afterwards but it seems to discuss different images?

Acceptance criteria

  • AC1: Documented steps to run containers can be followed

Suggestions


Related issues 2 (0 open2 closed)

Related to openQA Project - action #127091: openQA default container should provide a certificate for starting Resolvedmkittler2023-04-032023-04-26

Actions
Copied from QA - action #122908: [tools] openSUSE conference 2023 contributions size:MResolvedlivdywan2023-01-10

Actions
Actions #1

Updated by livdywan over 1 year ago

  • Copied from action #122908: [tools] openSUSE conference 2023 contributions size:M added
Actions #2

Updated by okurz over 1 year ago

  • Related to action #127091: openQA default container should provide a certificate for starting added
Actions #3

Updated by okurz over 1 year ago

  • Category set to Feature requests
  • Priority changed from Normal to Low
  • Target version set to Ready
Actions #4

Updated by mkittler over 1 year ago

This section already references the other documentation section that explains the Docker compose setup. It also states that these commands on its own are not very useful as they expect further parameters. So I'm not sure what you find ambiguous here and what you have expected.

Note that creating a setup where a single podman call allows to run "everything" (whatever this means exactly) within a single container is likely a bigger task than changing the documentation. However, I wouldn't recommend running all/multiple services in one container as it would be inconvenient to check logs and whether all required processes are still running as expected (compared to how nice this can be done with the docker compose setup).

Maybe we could at least add parameters for mounting the default self-signed certificate and config files. That shouldn't hurt.

Actions #5

Updated by mkittler over 1 year ago

  • Assignee set to mkittler
Actions #6

Updated by mkittler over 1 year ago

  • Status changed from New to Feedback
Actions #7

Updated by mkittler over 1 year ago

  • Status changed from Feedback to Resolved

The PR has been merged.

Actions

Also available in: Atom PDF