Problems building docker image using /workspace as root
Hello. I am trying to build my docker containers on runpod. I am using a Network Storage on the volume /workspace.
I installed docker, and set the root as /workspace/docker/ because it will take a lot of space
It was taking a long time, and we noticed the storage-driver was "vfs". So we tried to change it to "fuse-overlayfs" and seem to work, but when pulling Redis files (one of my containers is for Redis), it gave this error:
I tried running the modprobe and had this error:
I tried installing fuse and a bunch of packages, but nothing seems to work.
Does someone know how to add the "fuse", or do we need to use a different storage driver for Docker in the /workspace?
14 Replies
Do you need that? ( fs configuration)
Btw are you using cpu pods?
CPU pod yes
I have no idea about this sorry
You can't do it in a container, its a host level thing
im not sure what you are trying to do
Running an app using docker. I am using a CPU pod, with a Network Volume and assigning the Docker root to the volume, because this docker container takes more than 30Gb space
why just not make template ?
I think he's building docker images inside pods
Pretty sure Carla = she, not he
I see so she tries to build container and cause cpu pod limit is 20 GB she tries to store data on network storage for docker
Guess this is why people started adding pronouns to their profiles 🤷♂️
Sorry Carla didn't see your name
Try making a template for this redis image if you're only running an app using docker or are you using like compose or swarm?
compose, there are 2 containers (one is for redis)
It seems to be related to the network volume. I found an option to increase the container volume.
Using docker on the container volume works fine. I don't know why it does not work for the network volume, but I will close this since I can get the app to work now.
Thank you everyone! 😁
Yeah you can use more cpu to get more limits to the volume in cpu pods