Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
D
docker-registry
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
liugaoling
docker-registry
Commits
02091fb0
Commit
02091fb0
authored
Oct 21, 2021
by
liugaoling
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
updata data dir
parent
a59d131a
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
10 additions
and
1 deletion
+10
-1
README.md
README.md
+9
-0
docker-compose.yml
conf/docker-compose.yml
+1
-1
No files found.
README.md
View file @
02091fb0
# docker-registry
# docker-registry
1.
登录需要部署的服务器
2.
创建需要保存的数据的data目录,仓库文件可能过大,建议使用挂载(正常fileserver mkdir -p /public/registry/data)
3.
目录在docker-compose.yml文件中指定
4.
然后需要使用HTTPS,就需要证书文件,也在docker-compose.yml中配置
5.
在conf目录中,docker-compose up -d 即可
如果修改了main中的go文件,就需重新编译(需要go环境)
编译:
编译:
cd conf/extensions
cd conf/extensions
GOOS=linux GOARCH=386 go build ../../main/authentication.go
GOOS=linux GOARCH=386 go build ../../main/authentication.go
...
...
conf/docker-compose.yml
View file @
02091fb0
...
@@ -6,7 +6,7 @@ services:
...
@@ -6,7 +6,7 @@ services:
-
"
5000:5000"
-
"
5000:5000"
volumes
:
volumes
:
-
/root/ssl_certificate:/ssl:ro
-
/root/ssl_certificate:/ssl:ro
-
.
/data:/data
-
/public/registry
/data:/data
restart
:
always
restart
:
always
environment
:
environment
:
-
REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY=/data
-
REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY=/data
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment