[GH-ISSUE #596] Wallabag import script impossible to execute #313

New issue

Closed

opened 2026-02-25 23:33:56 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 23:33:56 +03:00

Owner

Originally created by @crawfordlong on GitHub (Mar 20, 2023).
Original GitHub issue: https://github.com/go-shiori/shiori/issues/596

Data

Shiori version: I believe it is 1.5.4 (docker)
Database Engine: n/a
Operating system: ubuntu
CLI/Web interface/Web Extension: n/a

Describe the bug / actual behavior

Documentation references a wallabag import bash script to import a wallabag json archive. The docker container is built without bash (i.e., docker exec -it shiori /bin/sh works but /bin/bash does not). The import script is therefore impossible to execute in a docker deployment.

Expected behavior

docker exec -it shiori /bin/bash then ./$scriptname works to import wallabag json archive.

To Reproduce

Steps to reproduce the behavior:

On the host docker exec -it shiori /bin/bash (fails)
On the host docker exec -it shiori /bin/sh (works)
./$scriptname fails because bash isn't available (I believe the script name is wallabag2shiori, but I can't confirm that where I am right now)

Originally created by @crawfordlong on GitHub (Mar 20, 2023). Original GitHub issue: https://github.com/go-shiori/shiori/issues/596 ## Data - **Shiori version**: I believe it is 1.5.4 (docker) - **Database Engine**: n/a - **Operating system**: ubuntu - **CLI/Web interface/Web Extension**: n/a ## Describe the bug / actual behavior Documentation references a wallabag import bash script to import a wallabag json archive. The docker container is built without bash (i.e., `docker exec -it shiori /bin/sh` works but `/bin/bash` does not). The import script is therefore impossible to execute in a docker deployment. ## Expected behavior `docker exec -it shiori /bin/bash` then ./$scriptname works to import wallabag json archive. ## To Reproduce Steps to reproduce the behavior: 1. On the host `docker exec -it shiori /bin/bash` (fails) 2. On the host `docker exec -it shiori /bin/sh` (works) 3. `./$scriptname` fails because bash isn't available (I believe the script name is wallabag2shiori, but I can't confirm that where I am right now)

kerem

2026-02-25 23:33:56 +03:00

closed this issue
added the
tag:stale
label

kerem commented

2026-02-25 23:33:56 +03:00

Author

Owner

@Monirzadeh commented on GitHub (Jul 1, 2023):

Hi
can you send a wallabag json sample for testing that?
In general, it is not a big problem. Docker image, use sh. and as you explain script work fine, so it is better if we just update document and be sure script work fine in sh too.

@Monirzadeh commented on GitHub (Jul 1, 2023): Hi can you send a wallabag json sample for testing that? In general, it is not a big problem. Docker image, use sh. and as you explain script work fine, so it is better if we just update document and be sure script work fine in sh too.

kerem commented

2026-02-25 23:33:56 +03:00

Author

Owner

@fmartingr commented on GitHub (Jan 1, 2025):

I added support in the CI to have alpine-vX.X.X tagged versions, which allow for a non-scratch OS to be run along Shiori. In that OS all required tooling can be installed using apk -update add. It's difficult to keep up with all third party scripts so right now this is the best way to interact with the docker image.

@fmartingr commented on GitHub (Jan 1, 2025): I added support in the CI to have `alpine-vX.X.X` tagged versions, which allow for a non-scratch OS to be run along Shiori. In that OS all required tooling can be installed using `apk -update add`. It's difficult to keep up with all third party scripts so right now this is the best way to interact with the docker image.

kerem commented

2026-02-25 23:33:56 +03:00

Author

Owner

@stale[bot] commented on GitHub (Jan 31, 2025):

This issue has been automatically marked as stale because it has not had any activity for quite some time.
It will be closed if no further activity occurs.
Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 31, 2025): This issue has been automatically marked as stale because it has not had any activity for quite some time. It will be closed if no further activity occurs. Thank you for your contributions.