You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/manual/images.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,9 +46,9 @@ With that we make a new image named `sros:20.10.R3` that references the same ori
46
46
47
47
### Pushing to a new registry
48
48
49
-
Same `docker tag` command can be used to rename the image so it can be pushed to another registry. For example consider the newly built SR OS 21.2.R1 [vrnetlab](vrnetlab.md) image that by default will have a name of `vrnetlab/vr-sros:21.2.R1`. This container image can't be pushed anywhere in its current form, but retagging will help us out.
49
+
That same `docker tag` command can be used to rename the image so it can be pushed to another registry. For example consider the newly built SR OS 21.2.R1 [vrnetlab](vrnetlab.md) image that by default will have a name of `vrnetlab/vr-sros:21.2.R1`. This container image can't be pushed anywhere in its current form, but retagging will help us out.
50
50
51
-
If we wanted to push this image to a public registry like Github Container Registry, we could do the following:
51
+
If we wanted to push this image to a public registry like the Github Container Registry, we could do the following:
52
52
53
53
```bash
54
54
# retag the image to a fully qualified name that is suitable for
0 commit comments