![]() One is that when I edit the hostname in those files things become separated between the hostname and the keyring. I mean, I can imagine two ways that things could go wrong on me. I'll google it right now though.Įdit: The keyring thing is kind of concerning to me also. Is there anything I can to to cover myself if some mistake were to be made and I got locked out of my computer or something? Is there some file or something I can save to my thumb drive or some way I could roll things back in case something goes wrong?Īlso I have never used recovery mode with Linux, nor have I ever read anything about how to do it or how it works. I'm having a hard time recalling which method I used to change the host name but I'm relatively certain I did that through the command line. ![]() That's the only way I know how to do that. I changed the password via the gui (system > administration > users and groups > ). Note: sudo works fine, it just complains, so you can edit it with the machine running instead of having to boot into recovery mode. Did you change your user account password from the commandline or via GUI?Īs for the "unable to resolve host" thing, it happens when you change hostnames.Įdit the /etc/hosts file and replace the old name with the new name. So the final docker-compose.yml looks like this: version: '3' I have found a solution: removing networks' definition. LOG: database system is ready to accept connections LOG: MultiXact member wraparound protections are now enabled LOG: database system was shut down at 07:02:04 UTC PostgreSQL Database directory appears to contain a database Skipping initialization I wonder if I must specify a driver for this situation.Īlso I would like a way to test if I can reach db service with this hostname from the container of web and so, if the problem is in the code (that I highly doubt but I want to be sure).ĮDIT1: Logs of db service showing that the service seems to be running fine and ready to accept connections $ sudo docker logs -f mastodon_db_1 I already used the combination of Docker-Compose and Podman 3.0 with several projects and I never had any issue with hostname resolving inside networks. ![]() PG::ConnectionBad: could not translate host name "db" to address: Name or service not known Generating secrets was fine, but it failed on this command: $ sudo docker-compose run -rm web bundle exec rails db:migrateĬreating network "mastodon_internal_network" with the default driverĬreating network "mastodon_external_network" with the default driver (tl dr: I added options to health-checks and an env variable to authorize running postgres without password and commented build option to use image from the repo, as building was failing too) $ git diff docker-compose.ymlĭiff -git a/docker-compose.yml b/docker-compose.yml ![]() Here is a diff with remote version of the file on the repository: # http_proxy= # ALLOW_ACCESS_TO_HIDDEN_SERVICE=true # Uncomment to enable federation with tor instances along with adding the following ENV variables elasticsearch:/usr/share/elasticsearch/dataĬommand: bash -c "rm -f /mastodon/tmp/pids/server.pid bundle exec rails s -p 3000" # image: /elasticsearch/elasticsearch-oss:6.8.10 I had to do some changes into the docker-compose.yml to make it work with Podman. You can see my whole config file below. $ docker-compose -versionĭocker-compose version 1.27.4, build unknown I am running Docker-Compose and Podman on a Fedora 33 server. I am trying to deploy a mastodon server using this project:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |