browser issues with the docker solution

[seemedFilm]

Hi folks,

I have an issue with the docker solution.
first of all I got the mounts working and the script found the config.yaml file.

This is the logfile I receive:

[INFO] Creating Browser session...
[INFO]  -> Browser binary location: /usr/bin/chromium
[INFO]  -> Chromium 136+ detected: Chromium 140.0.7339.185 (major: 140)
[INFO]  -> Chromium 136+ configuration validation passed
[INFO]  -> Custom Browser argument: --no-sandbox
[INFO]  -> Browser user data dir: cache
[ERROR] Failed to start browser. This error often occurs when:
[ERROR] 1. Running as root user (try running as regular user)
[ERROR] 2. Browser profile is locked or in use by another process
[ERROR] 3. Insufficient permissions to access the browser profile
[ERROR] 4. Browser binary is not executable or missing
[ERROR] 
[ERROR] Troubleshooting steps:
[ERROR] 1. Close all browser instances and try again
[ERROR] 2. Remove the user_data_dir configuration temporarily
[ERROR] 3. Try running without profile configuration
[ERROR] 4. Check browser binary permissions: /usr/bin/chromium
[ERROR] 5. Check if any antivirus or security software is blocking the browser
[ERROR] Exception: 
                ---------------------
                Failed to connect to browser
                ---------------------
                One of the causes could be when you are running as root.
                In that case you need to pass no_sandbox=True 

This is my docker run command:

docker run -it \
  --shm-size=256m \
  -e DISPLAY=:0 \
  -e KLEINBOT_NAME=kleinbot \
  -e KLEINBOT_LOGS=/docker/klein/bot/data/logs \
  -e KLEINBOT_DATA=/docker/klein/bot/data \
  -e KLEINBOT_CACHE=/docker/klein/bot/data/cache \
  -e SHARED_ADS=/docker/klein/shared/ads \
  -e SHARED_PIC=/docker/klein/shared/ads/pics \
  -v /docker/klein/shared/ads:/mnt/data/ads:rw \
  -v /docker/klein/shared/ads/pics:/mnt/data/ads/pics:rw \
  -v /docker/klein/bot/data/cache:/mnt/data/cache:rw \
  -v /docker/klein/bot/data/logs:/mnt/data/logs:rw \
  -v /docker/klein/bot/data:/mnt/data:rw \
  second-hand-friends/kleinanzeigen-bot:latest \
  publish

This is my config.yaml:

ad_files:
  - /mnt/data/ads/ad_*.{json,yml,yaml}
ad_defaults:
  active: true
  type: OFFER
  price_type: NEGOTIABLE
  shipping_type: SHIPPING
  sell_directly: false
  contact:
    name: 'John Doe'
    street: ''
    zipcode: 12345
    phone: '' # IMPORTANT: surround phone number with quotes to prevent removal of leading zeros
  republication_interval: 7
categories: {}
download:
  include_all_matching_shipping_options: false
  excluded_shipping_options: []
publishing:
  delete_old_ads: AFTER_PUBLISH
  delete_old_ads_by_title: true
browser:
  arguments:
    - --no-sandbox
  binary_location:
  extensions: []
  use_private_window: false
  user_data_dir: "/mnt/data/cache"
login:
  username: "[email protected]"
  password: "hfdghfgdhfgdhdgfhfdghfdghfdg"
captcha:
  auto_restart: false
  restart_delay: 6h
update_check:
  enabled: true
  channel: latest
  interval: 7d

The errormessage remains the same, even by using the following browser arguments:

browser:
  arguments:
    - --disable-dev-shm-usage
    - --no-sandbox
    - --headless

Since all three option dont work in this case, what options do I have?
Could it be an access right issue?
Can I start the container with an other user?

I have no clues currently

[seemedFilm]

I got it working with some adjustments:
config.yaml:

browser:
  arguments:
    - --no-sandbox
    - --remote-debugging-port=9222

docker run -it \
  --shm-size=1g \
  --remote-debugging-port=9222 \
  -p 9222:9222 \
.... ENV/VOL mounts

And now when I start chromium through another shell with:

/usr/bin/chromium \
  --headless=new \
  --no-sandbox \
  --disable-dev-shm-usage \
  --disable-gpu \
  --remote-debugging-port=9222 
  --user-data-dir=/mnt/data/cache \
  about:blank

The kleinanzeigen-bot can now connect to this instance.
It seems that the kleinanzeigen-bot script dont start chromium befor the bot starts.