Natal

Hello everyone,

Recently found LinguaCafe and decided to spin it up. There's a provided docker-compose with just volumes to specify to your own taste. Pretty easy right?

I can't make it work. Spent nearly two hours already trying to figure out what I'm missing.

Can someone take a look at my compose file and tell me where I'm stupid?

_____________ EDITS

Progress has been made, I used chmod 777 on the whole app directory and now get the following error : Illuminate\Database\QueryException SQLSTATE[HY000] [1045] Access denied for user 'linguacafe'@'ip adress censored' (using password: YES) (SQL: select count(*) as aggregate from users)

Here's a somewhat anonymized pastebin, I just removed the password and my name from the file. The rest is basically the file provided by the github + my paths. https://pastebin.com/u2cbWm2n

https://github.com/simjanos-dev/LinguaCafe

What happens is, my containers spin up apparently properly. But when I go to :9191, I have this:

https://imgur.com/a/PiazCcP

I did sudo chmod 777 /home/user/Documents/Docker/LinguaCafe/temp -R as instructed by the documentation.

Never had that happen before. Does anyone know? Thanks

Update Oct 6 :

I have been messing around the idea of permissions but just got back from work so this is very much Work In Progress. What I noticed is that the "postgres" folder inside the Docker folder that has the docker-compose file had a lock icon on it. https://imgur.com/a/lZir4tt The owner is weird and doesn't exist on the other computer. I don't explain how this owner was created and that may be due to my poor understanding of Docker and docker-compose.

So I have made a pastebin with the docker compose here if anyone is interested in this little puzzle : https://pastebin.com/Vsh6S23G This docker-compose is basically the one from the installation guide from the app website, I just changed some passwords and users related stuff which are written as .

I tried using Déjà Dup Backups to sync my entire Docker folder which also contains Tandoor and it complained it could not sync the postgres folder either so defo something wrong with the permissions. Which explains why I can't create a new recipe on the other computer, because it doesn't have permission for that specific task. Oddly enough, I get a server 500 error, but if I refresh the recipe list, the new recipe that led to the server 500 error is, actually, there.

Would a pastebin of the .env help?

ORIGINAL POST :

Hello again, I hope it's okay that I make several posts in a rather short time, I'm stumped.

I run a series of containers on old computer A for the recipe manager Tandoor Recipes.

I want to move it to another computer B so I initially thought I would: -copy the env and docker-compose -dump the source database

Move everything to the new computer, compose everything and fill the database from the dump.

I got 500 server errors so I went on Discord and asked what was the proper way of doing this. I've been told in theory I could shut everything down, pack my Tandoor folder in a zip, paste it on the target computer B and boot everything and voilà.

None of this works properly.

I do manage to get an instance of Tandoor running on my new computer, it displays every recipe I had originally, but it has an issue when trying to create a new recipe. I get a white page with "Server Error (500)". It does not happen on the original Tandoor, despite being all the same files in theory.

I noticed that on my source computer, the postgres DB directory changes permission when I start the container, as well as the directory containing the recipe pictures. So I'm wondering if wrong permissions might be corrupting data while copying stuff?

Thanks

Hello everyone,

I have containers that I want to get rid of because I can't make them work, but I can't seem to get rid of them. I'm using Portainer usually and the remove command on the container works, but they shortly reappear as newly created containers.

I moved to the terminal to try and sudo it out of existence manually, docker ps, the containers are here. So I sudo docker stop , the terminal confirms. Then sudo rm -f , confirmed again.

Docker ps shows they are gone, but a minute later another docker ps shows they are back up again.

I've looked it up online and people mentioned it might be running as a service. The command "docker service ls" returns an empty list.

How can I nuke those containers?

Does it happen to anyone else and does anyone know why it happens and if it means it's gone bad or it's safe?

It's the only spice in my kitchen, and I have many, that acts weird and google wasn't helpful on this one.

It becomes one solid block at the bottom and I would need a knife or something sharp to go tear at it and break clumps off from it again. But I'm not sure it's still safe to eat.