Move from hard drisk to solid state for containers #25

New Issue

sickprodigy · 2023-12-15T07:57:45-05:00

sickprodigy commented

2023-12-15 07:57:45 -05:00

Containers may be moving slow because all the information for them are situated on hard disk.

I've gotten a real fast ssd, and want to try the speeds from it instead of hard disk.

Containers may be moving slow because all the information for them are situated on hard disk. I've gotten a real fast ssd, and want to try the speeds from it instead of hard disk.

sickprodigy commented

2023-12-15 07:58:06 -05:00

Method: # 12/15/23

docker stop $(docker ps -a -q)   # Halt all containers
rsync -avzP /srv/samba/media/Documents/prodigy/Coding-Programming/docker-containers/ /home/terry/Documents/docker-containers
rsync -avzP /home/terry/Documents/plex/ /home/terry/Documents/docker-containers/plex

cd /var/lib/docker/network/files/
mv local-kv.db local-kv.db.backup

cd /var/lib/docker/network/files/
mv local-kv.db local-kv.db.backup
sudo service docker restart

This command didn't work right, would be nice if it did though...

docker network create \
   --subnet=10.11.0.0/16 \
   --gateway=192.168.10.100 \
   --opt "com.docker.network.bridge.host_binding_ipv4"="192.168.86.22" \
   homelab


Ran this instead: docker network create homelab

Can't find the damn network still... probably because i ran that first command multi line.

cd /srv/samba/media/Documents/prodigy/Coding-Programming/docker-containers/portainer-be    # go to portainer directory, start up. Need to know Ip to get back to it
cd /home/terry/Documents/docker-containers/portainer-be
docker compose up -d
docker compose up -d --force-recreate # succeeded
http://192.168.86.185:9110/#!/auth
Start nginx, then the rest

Need to edit portainer stacks to reflect changed location. or maybe mount will just cause it not to care idk. rename folder -backup and restart and see what happens
Didn't have to edit since I bind mounted from terry to prodigy. Worked out great

Method: # 12/15/23 ``` docker stop $(docker ps -a -q) # Halt all containers rsync -avzP /srv/samba/media/Documents/prodigy/Coding-Programming/docker-containers/ /home/terry/Documents/docker-containers rsync -avzP /home/terry/Documents/plex/ /home/terry/Documents/docker-containers/plex cd /var/lib/docker/network/files/ mv local-kv.db local-kv.db.backup cd /var/lib/docker/network/files/ mv local-kv.db local-kv.db.backup sudo service docker restart This command didn't work right, would be nice if it did though... docker network create \ --subnet=10.11.0.0/16 \ --gateway=192.168.10.100 \ --opt "com.docker.network.bridge.host_binding_ipv4"="192.168.86.22" \ homelab Ran this instead: docker network create homelab Can't find the damn network still... probably because i ran that first command multi line. cd /srv/samba/media/Documents/prodigy/Coding-Programming/docker-containers/portainer-be # go to portainer directory, start up. Need to know Ip to get back to it cd /home/terry/Documents/docker-containers/portainer-be docker compose up -d docker compose up -d --force-recreate # succeeded http://192.168.86.185:9110/#!/auth Start nginx, then the rest Need to edit portainer stacks to reflect changed location. or maybe mount will just cause it not to care idk. rename folder -backup and restart and see what happens Didn't have to edit since I bind mounted from terry to prodigy. Worked out great ```

sickprodigy closed this issue

2023-12-15 07:58:06 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: sickprodigy/home-server#25