Separated images, attached same volume and port mapping
This commit is contained in:
parent
81b6cee363
commit
15b9955f98
9
Dockerfile_backend
Normal file
9
Dockerfile_backend
Normal file
@ -0,0 +1,9 @@
|
|||||||
|
FROM ubuntu:22.04
|
||||||
|
|
||||||
|
COPY ./deb-files/backend-flo_0.15.1.1-satoshilabs-1_amd64.deb /opt/backend.deb
|
||||||
|
|
||||||
|
RUN apt update && apt install -y /opt/backend.deb
|
||||||
|
WORKDIR /opt/coins/nodes/flo
|
||||||
|
RUN sed -i 's/daemon=1/daemon=0/' /opt/coins/nodes/flo/flo.conf
|
||||||
|
|
||||||
|
ENTRYPOINT ["/opt/coins/nodes/flo/bin/flod", "-datadir=/opt/coins/data/flo/backend", "-conf=/opt/coins/nodes/flo/flo.conf", "-pid=/run/flo/flo.pid"]
|
||||||
8
Dockerfile_frontend
Normal file
8
Dockerfile_frontend
Normal file
@ -0,0 +1,8 @@
|
|||||||
|
FROM ubuntu:22.04
|
||||||
|
|
||||||
|
COPY ./deb-files/blockbook-flo_0.4.0_amd64.deb /opt/blockbook.deb
|
||||||
|
|
||||||
|
RUN apt update && apt install -y /opt/blockbook.deb
|
||||||
|
WORKDIR /opt/coins/blockbook/flo
|
||||||
|
|
||||||
|
ENTRYPOINT ["/opt/coins/blockbook/flo/bin/blockbook", "-blockchaincfg=/opt/coins/blockbook/flo/config/blockchaincfg.json", "-datadir=/opt/coins/data/flo/blockbook/db", "-sync", "-internal=:9066", "-public=:9166", "-certfile=/opt/coins/blockbook/flo/cert/blockbook", "-explorer=", "-log_dir=/opt/coins/blockbook/flo/logs", "-dbcache=1073741824"]
|
||||||
27
README.md
27
README.md
@ -2,8 +2,31 @@
|
|||||||
|
|
||||||
## Roadmap for upgrade
|
## Roadmap for upgrade
|
||||||
|
|
||||||
[ ] - Create separate images for both backend and blockbook.
|
[X] - Create separate images for both backend and blockbook.
|
||||||
[ ] - Attach the same volume to both the running containers of the images.
|
[X] - Attach the same volume to both the running containers of the images.
|
||||||
[ ] - Think of how Blockbook container will detect the spots of backend container
|
[ ] - Think of how Blockbook container will detect the spots of backend container
|
||||||
[ ] - See if creating a new network for both the containers will be a good option.
|
[ ] - See if creating a new network for both the containers will be a good option.
|
||||||
|
|
||||||
|
## Building & running backend image
|
||||||
|
|
||||||
|
```
|
||||||
|
docker build -t vivekteega/blockbook-backend:1.0.0 -f Dockerfile_backend .
|
||||||
|
|
||||||
|
docker volume create blockbook
|
||||||
|
|
||||||
|
docker run -it --mount source=blockbook,target=/opt/coins -p vivekteega/blockbook-backend:1.0.
|
||||||
|
|
||||||
|
docker run -d --mount source=blockbook,target=/opt/coins -p 38366:38366 -p 8066:8066 vivekteega/blockbook-backend:1.0.0
|
||||||
|
```
|
||||||
|
|
||||||
|
## Building & running frontend image
|
||||||
|
|
||||||
|
```
|
||||||
|
docker build -t vivekteega/blockbook-frontend:1.0.0 -f Dockerfile_frontend .
|
||||||
|
|
||||||
|
docker run -it --mount source=blockbook,target=/opt/coins -p 9166:9166 -p 9066:9066 vivekteega/blockbook-frontend:1.0.0
|
||||||
|
|
||||||
|
docker run -d --mount source=blockbook,target=/opt/coins -p 9166:9166 -p 9066:9066 vivekteega/blockbook-frontend:1.0.0
|
||||||
|
```
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
BIN
deb-files/backend-flo_0.15.1.1-satoshilabs-1_amd64.deb
Normal file
BIN
deb-files/backend-flo_0.15.1.1-satoshilabs-1_amd64.deb
Normal file
Binary file not shown.
BIN
deb-files/blockbook-flo_0.4.0_amd64.deb
Normal file
BIN
deb-files/blockbook-flo_0.4.0_amd64.deb
Normal file
Binary file not shown.
Loading…
Reference in New Issue
Block a user