File tree Expand file tree Collapse file tree 2 files changed +23
-3
lines changed Expand file tree Collapse file tree 2 files changed +23
-3
lines changed Original file line number Diff line number Diff line change @@ -90,11 +90,14 @@ volumes:
90
90
o : bind
91
91
` ` `
92
92
93
- Then build and run all services (-d is to run in background)
93
+ Then build and run all services (-d is to run in background)
94
+
94
95
` sudo docker-compose up -d`
95
96
96
97
You can check the web and the mariadb containers are up and see logs with
98
+
97
99
` sudo docker-compose ps`
100
+
98
101
` sudo docker-compose logs`
99
102
100
103
Once the log shows that the start is complete, go to http://0.0.0.0 to access to the new Dolibarr installation, first admin login is admin/admin.
@@ -116,15 +119,22 @@ You can find several examples in the `examples` directory, such as:
116
119
Warning : Only data stored into persistent directories will not be lost after an upgrade of containers.
117
120
118
121
Remove the `install.lock` file. The `install.lock` file is located inside the container volume `/var/www/documents`.
122
+
119
123
` sudo docker exec nameofwebcontainer bash -c "rm -f /var/www/documents/install.lock"`
120
- of
124
+
125
+ or
126
+
121
127
` sudo docker exec -it nameofwebcontainer bash`
128
+
122
129
` rm -f /var/www/documents/install.lock; exit`
123
130
124
131
125
132
Then start an updated version container.
133
+
126
134
` sudo docker-compose pull`
135
+
127
136
` sudo docker-compose up -d`
137
+
128
138
` sudo docker-compose logs`
129
139
130
140
Ensure that env `DOLI_INSTALL_AUTO` is set to `1` so it will migrate Database to the new version.
Original file line number Diff line number Diff line change @@ -85,10 +85,13 @@ volumes:
85
85
```
86
86
87
87
Then build and run all services (-d is to run in background)
88
+
88
89
`sudo docker-compose up -d`
89
90
90
91
You can check the web and the mariadb containers are up and see logs with
92
+
91
93
`sudo docker-compose ps`
94
+
92
95
`sudo docker-compose logs`
93
96
94
97
Once the log shows that the start is complete, go to http://0.0.0.0 to access to the new Dolibarr installation, first admin login is admin/admin.
@@ -110,15 +113,22 @@ You can find several examples in the `examples` directory, such as:
110
113
Warning: Only data stored into persistent directories will not be lost after an upgrade of containers.
111
114
112
115
Remove the `install.lock` file. The `install.lock` file is located inside the container volume `/var/www/documents`.
116
+
113
117
`sudo docker exec nameofwebcontainer bash -c "rm -f /var/www/documents/install.lock"`
114
- of
118
+
119
+ or
120
+
115
121
`sudo docker exec -it nameofwebcontainer bash`
122
+
116
123
`rm -f /var/www/documents/install.lock; exit`
117
124
118
125
119
126
Then start an updated version container.
127
+
120
128
`sudo docker-compose pull`
129
+
121
130
`sudo docker-compose up -d`
131
+
122
132
`sudo docker-compose logs`
123
133
124
134
Ensure that env `DOLI_INSTALL_AUTO` is set to `1` so it will migrate Database to the new version.
You can’t perform that action at this time.
0 commit comments