mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #1585] Bug: Setting Up a Chromium User Profile Docker Desktop Windows Perms Errors #3962
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#3962
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @pilotkrc on GitHub (Nov 5, 2024).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1585
Originally assigned to: @pirate on GitHub.
Provide a screenshot and describe the bug
archivebox.io has a Working Around Sites that Block Archiving section to archive sites that actively work against snapshots such as websites behind Cloudflare. This includes a few different methods but for this bug report, the CHROME_USER_DIR link that demonstrates how to setup a Chromium profile.
My instance is running via docker compose on Docker Desktop Windows and this works fine until Step 3 of the provided Docker VNC guide but then hits a dead-end. This is the
docker compose run archivebox /usr/bin/chromium-browser --user-data-dir=/data/personas/Default/chrome_profile --profile-directory=Default --disable-gpu --disable-features=dbus --disable-dev-shm-usage --start-maximized --no-sandbox --disable-setuid-sandbox --no-zygote --disable-sync --no-first-runcommand which I attempted to run via the docker desktop's terminal.I have tried to troubleshoot already using:
Steps to reproduce
docker compose up -d novncLogs or errors
ArchiveBox Version
How did you install the version of ArchiveBox you are using?
Docker (or other container system like podman/LXC/Kubernetes or TrueNAS/Cloudron/YunoHost/etc.)
What operating system are you running on?
Windows (including WSL, WSL2, Docker Desktop on Windows)
What type of drive are you using to store your ArchiveBox data?
data/is on a local SSD or NVMe drivedata/is on a spinning hard drive or external USB drivedata/is on a network mount (e.g. NFS/SMB/CIFS/etc.)data/is on a FUSE mount (e.g. SSHFS/RClone/S3/B2/OneDrive, etc.)Docker Compose Configuration
ArchiveBox Configuration
@pirate commented on GitHub (Nov 5, 2024):
You've already tried everything I would try, I don't have many ideas unfortunately.
Maybe some other SMB / users can chip in and offer advice? Does SMB implement locking like Unix filesystems do, perhaps chrome on Linux is expecting Unix file locking to work and is failing when the underlying drive doesn't support it?
@nguyenmp commented on GitHub (Nov 18, 2024):
Just curious, does this error occur when you run against a new clean
/data/folder?Also, try running
docker compose run -it --remove-orphans archivebox /bin/ls -liah /data/personas/Default/chrome_profile/. I suspect either the directory permissions are wrong (like wrong owner or user) or a lock already exists.For me, I saw the following files which prevented me from launching:
To remove those three lines:
@danielcrafts commented on GitHub (Jun 7, 2025):
Hi, i had the same issue.
Its working after changing the owner of the folder and subfolder.
BR,
Daniel