920+ running DSM 6.2.4-25556
I added 1xSSD (/volume2) to my existing 2xHDD (/volume1) this week. I moved my docker setup from /volume1/docker (HDD) to /volume2/docker (SSD) by following these steps:
- Stopped all my docker containers
- Stopped docker in Package Manager
- Backed up /volume1/docker via HyperBackup
- In Shared Folder I changed volume from /volume1/docker to /volume2/docker
- So far, so good...
- Once move was complete, I started docker and then went into the UI and modified Portainer to use /volume2/docker
- The Syno Docker UI complained ports 8000/9000 were already in use despite no other containers running at all
- When I encountered this port issue I reverted back to /volume1/docker and Portainer started without complaint
- I then repeated the steps above and the Syno Docker UI complained again when I tried bringing up Portainer
- I changed the Portainer ports to 8001:8000 and 9001:9000 and the container started with no issue.
Question 1:
Any idea why Portainer in this case is complaining about the ports already being in use?
Question 2:
I edited all the docker-compose files to point to /volume2/docker/container_name and that seems to all be fine. I noticed my containers still refer back to the original /volume1/@docker directory. Is there any way to have this point to /volume2 instead?
Here is an example from Portainer:
HostConfig section:
HostnamePath /volume1/@docker/containers/6dcb772373346d89fc627feaa73bc6b133e21aec1c0e84773518faa2dcbda90e/hostname
HostsPath /volume1/@docker/containers/6dcb772373346d89fc627feaa73bc6b133e21aec1c0e84773518faa2dcbda90e/hosts
Id 6dcb772373346d89fc627feaa73bc6b133e21aec1c0e84773518faa2dcbda90e
Image sha256:8377e6877145988a508c616a6cbf1f9659ab6093da69f74179c5e01581d8b8b1
LogPath /volume1/@docker/containers/6dcb772373346d89fc627feaa73bc6b133e21aec1c0e84773518faa2dcbda90e/log.db
Mount section:
Destination /config
Mode rw
Propagation rprivate
RW true
Source /volume2/docker/prowlarr
Type bind
Any insight would be greatly appreciated, thank you.
I added 1xSSD (/volume2) to my existing 2xHDD (/volume1) this week. I moved my docker setup from /volume1/docker (HDD) to /volume2/docker (SSD) by following these steps:
- Stopped all my docker containers
- Stopped docker in Package Manager
- Backed up /volume1/docker via HyperBackup
- In Shared Folder I changed volume from /volume1/docker to /volume2/docker
- So far, so good...
- Once move was complete, I started docker and then went into the UI and modified Portainer to use /volume2/docker
- The Syno Docker UI complained ports 8000/9000 were already in use despite no other containers running at all
- When I encountered this port issue I reverted back to /volume1/docker and Portainer started without complaint
- I then repeated the steps above and the Syno Docker UI complained again when I tried bringing up Portainer
- I changed the Portainer ports to 8001:8000 and 9001:9000 and the container started with no issue.
Question 1:
Any idea why Portainer in this case is complaining about the ports already being in use?
Question 2:
I edited all the docker-compose files to point to /volume2/docker/container_name and that seems to all be fine. I noticed my containers still refer back to the original /volume1/@docker directory. Is there any way to have this point to /volume2 instead?
Here is an example from Portainer:
HostConfig section:
HostnamePath /volume1/@docker/containers/6dcb772373346d89fc627feaa73bc6b133e21aec1c0e84773518faa2dcbda90e/hostname
HostsPath /volume1/@docker/containers/6dcb772373346d89fc627feaa73bc6b133e21aec1c0e84773518faa2dcbda90e/hosts
Id 6dcb772373346d89fc627feaa73bc6b133e21aec1c0e84773518faa2dcbda90e
Image sha256:8377e6877145988a508c616a6cbf1f9659ab6093da69f74179c5e01581d8b8b1
LogPath /volume1/@docker/containers/6dcb772373346d89fc627feaa73bc6b133e21aec1c0e84773518faa2dcbda90e/log.db
Mount section:
Destination /config
Mode rw
Propagation rprivate
RW true
Source /volume2/docker/prowlarr
Type bind
Any insight would be greatly appreciated, thank you.