Docker won't start #726
Comments
|
Unfortunately I'm not familiar with Docker... But yeah, Normally / without Docker, this config file is dynamically generated with the |
|
Hey.. thanks for getting back so quick! I don't really know Docker either :) I'll try to mess with it and see what I come up with. I'll send a PR if I can actually make Docker work. |
|
@benpate Is the |
|
One thing I have noticed with docker is, if the file doesn't already exist, I haven't tried running writefreely in docker yet, so I can't say for sure this will work for it, but try removing the directory and then |
|
That's right, Docker (and Podman) will generate a directory with the volume name if it doesn't exist and if it starts with A config file can be generated for Podman at least with the instructions of this PR, in "Making the writefreely-config.ini". Something similar should work with Docker I suppose. Here's a sample file with a few database things added: Click to see file[server]
hidden_host =
port = 8080
bind = localhost
tls_cert_path =
tls_key_path =
autocert = false
templates_parent_dir =
static_parent_dir =
pages_parent_dir =
keys_parent_dir =
hash_seed =
gopher_port = 0
[database]
type = mysql
filename =
username = writefreely
password = writefreelypass
database = writefreelydb
host = writefreely-db
port = 3306
tls = false
[app]
site_name =
site_description =
host = http://localhost:8080
theme = write
editor =
disable_js = false
webfonts = true
landing =
simple_nav = false
wf_modesty = false
chorus = false
forest = false
disable_drafts = false
single_user = true
open_registration = false
open_deletion = false
min_username_len = 3
max_blogs = 1
federation = true
public_stats = true
monetization = false
notes_only = false
private = false
local_timeline = false
user_invites =
default_visibility =
update_checks = false
disable_password_auth = false
[oauth.slack]
client_id =
client_secret =
team_id =
callback_proxy =
callback_proxy_api =
[oauth.writeas]
client_id =
client_secret =
auth_location =
token_location =
inspect_location =
callback_proxy =
callback_proxy_api =
[oauth.gitlab]
client_id =
client_secret =
host =
display_name =
callback_proxy =
callback_proxy_api =
[oauth.gitea]
client_id =
client_secret =
host =
display_name =
callback_proxy =
callback_proxy_api =
[oauth.generic]
client_id =
client_secret =
host =
display_name =
callback_proxy =
callback_proxy_api =
token_endpoint =
inspect_endpoint =
auth_endpoint =
scope =
allow_disconnect = false
map_user_id =
map_username =
map_display_name =
map_email = IMO it makes sense to have a sample config in the repository itself so users don't have to resort to automatic generation. It seems it was removed in 0eb1a2d#diff-03c62cb3e26f06d4d8277f11504a5121def68db562388cd769c2c6aaa234a811 for whatever reason. FWIW I just pushed this: https://github.com/herzenschein/herz-podman/tree/main/writefreely. That's a WIP showing how far I managed to go with a modified compose file. Hope it helps. |
|
The compose file I created and linked above is now functional, in addition to mentioning instructions and encountered errors. A PR will only be coming later, because I did this in my spare time. I saw several potential improvements that can be done to the upstream Dockerfile, but that will have to be taken care of later. |
|
Hey, any updates on this as far as a PR? Would love to get this resolved for the next release. |
|
I just made writefreely/documentation#50 (which actually solves this issue) and #784 (which just provides a few QoL fixes), but I'd like to test it one last time to confirm that I set the SELinux flags right and that the generated network name is correct for Docker and Podman. I have to read the CLA too. I'll be busy for a while, though, so if someone else can test it it would be helpful. More importantly, I also noticed that the container documentation is actually not reachable through the main website, as https://writefreely.org/docs is broken, install only mentions the standard installation, and I couldn't find a pathway from the mainpage to the Docker page. |
|
@herzenschein still need someone to test your release? Ping me and I'll look into it in the coming week(s). |
I'm trying to fire up WriteFreely in a Docker container using the instructions on the website. It seems to go pretty smoothly when I run
docker-compose up -dbut then thewritefreely-webinstance won't start, which prevents me from running the./docker-setup.shcommand.The logs look like this:
Sure enough, when I go to the WriteFreely directory, there's a new folder called
config.ini-- which doesn't seem right.This seems to be created by the docker-compose.yml, with this config:
Am I doing something wrong? Or is there a simple fix?
The text was updated successfully, but these errors were encountered: