Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: upgrading Docker image from 0.7.2 to 0.7.4 - The 0.7.4 version doesn't work #1393

Closed
Eliastik opened this issue Mar 30, 2024 · 3 comments

Comments

@Eliastik
Copy link

Eliastik commented Mar 30, 2024

Describe the bug

When upgrading the Docker image from version 0.7.2 to 0.7.4, the container don't work anymore and crash with an error in the logs.

Downgrading to 0.7.2 fixes this issue.

Steps to reproduce

Spawn a container with this docker-compose.yml file:

# Usage:
#     docker-compose run archivebox init --setup
#     docker-compose up
#     echo "https://example.com" | docker-compose run archivebox archivebox add
#     docker-compose run archivebox add --depth=1 https://example.com/some/feed.rss
#     docker-compose run archivebox config --set PUBLIC_INDEX=True
#     docker-compose run archivebox help
# Documentation:
#     https://github.com/ArchiveBox/ArchiveBox/wiki/Docker#docker-compose

version: '2.4'

services:
    archivebox:
        # build: .                              # for developers working on archivebox
        image: ${DOCKER_IMAGE:-archivebox/archivebox:0.7.4}
        command: server --quick-init 0.0.0.0:8000
        restart: unless-stopped
        ports:
            - 8000:8000
        environment:
            - ALLOWED_HOSTS=*                   # add any config options you want as env vars
            - MEDIA_MAX_SIZE=750m
            # - CHROME_HEADLESS=False
            # - CHROME_USER_DATA_DIR=/home/archivebox/.config/chromium
            # - SEARCH_BACKEND_ENGINE=sonic     # uncomment these if you enable sonic below
            # - SEARCH_BACKEND_HOST_NAME=sonic
            # - SEARCH_BACKEND_PASSWORD=SecretPassword
        volumes:
            - ./data:/data
            # - ./archivebox:/app/archivebox    # for developers working on archivebox

Screenshots or log output

The log is :

[i] [2024-03-30 11:04:05] ArchiveBox v0.7.3: archivebox server --quick-init 0.0.0.0:8000
    > /data

[X] Could not find profile "Default" in CHROME_USER_DATA_DIR.
    /data/personas/Default/chromium
    Make sure you set it to a Chrome user data directory containing a Default profile folder.
    For more info see:
        https://github.com/ArchiveBox/ArchiveBox/wiki/Configuration#CHROME_USER_DATA_DIR

    Try removing /Default from the end e.g.:
Traceback (most recent call last):
  File "/usr/local/bin/archivebox", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/app/archivebox/cli/__init__.py", line 140, in main
    run_subcommand(
  File "/app/archivebox/cli/__init__.py", line 74, in run_subcommand
    setup_django(in_memory_db=subcommand in fake_db, check_db=cmd_requires_db and not init_pending)
  File "/app/archivebox/config.py", line 1389, in setup_django
    check_system_config()
  File "/app/archivebox/config.py", line 1297, in check_system_config
    stderr('        CHROME_USER_DATA_DIR="{}"'.format(config['CHROME_USER_DATA_DIR'].split('/Default')[0]))
                                                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'PosixPath' object has no attribute 'split'

ArchiveBox version

0.7.4 (Docker version) on Ubuntu 20.04.6 LTS host

@Eliastik Eliastik changed the title Bug: upgrading Docker image from 0.7.2 to 0.7.4 - The 0 Bug: upgrading Docker image from 0.7.2 to 0.7.4 - The 0.7.4 version doesn't work Mar 30, 2024
@pirate
Copy link
Member

pirate commented Mar 30, 2024

Duplicate: #1391

Temporary solution is mentioned in that issue. Should be fixed in a few days.

@pirate pirate closed this as completed Mar 30, 2024
@dsander
Copy link

dsander commented Mar 30, 2024

@pirate I am having the same problem as described by the OP, the issue you linked seems to be related to the :dev tag or having the CHROME_USER_DATA_DIR environment variable set. Am I missing the actual workaround?

@pirate
Copy link
Member

pirate commented Apr 10, 2024

I fixed the broken Docker tags: :dev, :0.7, or :0.7.2 should point to the working previous release again. Sorry for the trouble!

I'll also fix that CHROME_USER_DATA_DIR error / make sure it's a quieter warning if it's actually set wrong: #1425

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants