docker compose deployment problem
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, docker-compose, mariadb, redis
- Domain
- devops, infrastructure
Research direction
Start with docker-compose.yml and the wallabag/wallabag:2.4.2, mariadb, and redis services. Reproduce the deployment on Ubuntu 20.04, then collect the missing error output and environment details; what counts as done cannot be defined until the failure is specified.
Written by the indexing model from the issue text.
Description
Environment
cat docker-compose.yml
version: '3'
services:
wallabag:
image: wallabag/wallabag:2.4.2
# 相当于docker pull wallabag/wallabag
container_name: wallabag
depends_on:
- db
- redis
ports:
- 12488:80 #
environment:
- MYSQL_ROOT_PASSWORD=wallaroot
- SYMFONY__ENV__DATABASE_DRIVER=pdo_mysql
- SYMFONY__ENV__DATABASE_HOST=db
- SYMFONY__ENV__DATABASE_PORT=3306
- SYMFONY__ENV__DATABASE_NAME=wallabag
- SYMFONY__ENV__DATABASE_USER=wallabag
- SYMFONY__ENV__DATABASE_PASSWORD=wallapass
- SYMFONY__ENV__DATABASE_CHARSET=utf8mb4
- SYMFONY__ENV__MAILER_HOST=~
- SYMFONY__ENV__MAILER_USER=~
- SYMFONY__ENV__MAILER_PASSWORD=~
- [email protected] #
- SYMFONY__ENV__DOMAIN_NAME=http://ip #
volumes: #
- /volume1/docker/wallabag/images:/var/www/wallabag/web/assets/images
- /volume1/docker/wallabag/data:/var/www/wallabag/data
restart: always
db:
image: mariadb
container_name: wallabag_mariadb
environment:
- MYSQL_ROOT_PASSWORD=wallaroot
volumes: #
- /volume1/docker/wallabag/mysql:/var/lib/mysql
restart: always
redis:
image: redis:alpine
container_name: wallabag_redis
restart: always
- Version:
- Installation:
- PHP version:
- OS:
- Database:
- Parameters:
My app/config/parameters.yml is:
PASTE HERE
What steps will reproduce the bug?
- Dominant language
- Shell
- Stars
- 771
- Forks
- 168
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from wallabag/docker
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 57/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Awaiting response
Difficulty 4/5 3-5 days Newbie friendliness 32/100
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
Similar issues
-
数据界面的横向滚动条缺失Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
zilliztech/attu#1037 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
alunduil/alunduil-chezmoi#964 ·
Maintainers usually reply within 1 day
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
[pico][astrocade] emu/apply.sh edits src/mame/midway/astrohome.cpp, which current MAME has in bally/Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
FujiNetWIFI/fujinet-firmware#2120 ·
Maintainers usually reply within 1 day