Newbie needs a lille help :)

[ronnie2903]

Hi

I am all new to this, and have tried to consume all the knowledge i can find on the web, but i have run into some issues, that i simply can't figure out.

i was trying to make a docker container for a FileCloud instalation. I saw this youtube video https://www.youtube.com/watch?v=xBIowQ0WaR8&list=WL&index=11&t=1025s&ab_channel=NetworkChuck and decided to try it out. I got to make the container run, but everytime i follow the steps in the FileCloud installation guide, it get some messages i do not understand, and all looks so simple when looking it up on the web, i just can't make it work.

Then i read some info about the sudo command (as this wasn't working ether), but for what i can find on the web bout installing sudo, it simply doesn't work for me.. so yeah i'm kinda locked down, i hope someone could guide me in the right direction.

i have done a screendumb here that showes my current progress, hope that helps on understanding.

 

[sretalla]

I guess nobody has stepped in to help yet as there isn't enough information on what you have done without watching that video, (which at least I personally don't have time or energy for), so perhaps you can summarize what you did a little so we can understand why you're trying to run docker-compose in a pod shell that seems to not have some of the tools you need.

What pod is it that you're running there?

 

[ronnie2903]

yeah you're right, i got much to learn.. sorry

The video wasn't really ment for you to watch, just to make a context.

i have made the container with following app

i am sorry if i am just simply missunderstanding something, but yeah when i try to run the command "docker-compose up -d filecloud.server filecloud.mongodb" it simply says "read /: is a directory" when i watch the setup youtube, it here starts downloading a lot of stuff, mine is just not doing it.

when i do sudo before it just says "/bin/sh: sudo: not found

 

[sretalla]

OK, so with the docker-compose app pod already running, you've tried to download the docker-compose.yml file, but failed as it was already there... maybe ls -l would help to see that.

Also, that app was sort-of designed to auto-launch a docker-compose.yml (specified in the "Docker compose file" field in the app setup), which you should place on the host, but add into the pod with persistent storage settings, ideally with matching paths to avoid confusion.

So where you are is in the filesystem root / , so it's probably not the best, but in any case, you can get around the problem by telling docker-compose the location of the file it isn't finding:

docker compose -f docker-compose.yml up