[bin/up] docker-compose script failed to recongnise the customized docker image name. · Issue #352 · overleaf/toolkit · GitHub
More Web Proxy on the site http://driver.im/
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
OS: CentOS 7.9
problem: Cannot save docker image with custominzed name(TAG)
description: Hi bros,I cannot customize the name of docker images, it said “ERROR: invalid version '5.4.0-with-texlive-xelatex-full-and-chinese-support'”,I just commit a new docker image by adding CN font and XeLaTeX full repair, naming the image "5.4.0-with-texlive-xelatex-full-and-chinese-support", only "a.b.c" name functioned, like 5.4.0 as well as the latest version of ShareLaTeX.
I will greatly appreciate it if someone tells me the reason, thx~
The text was updated successfully, but these errors were encountered:
Lyrlark
changed the title
[bin/up]
[bin/up] docker version failed to recongnise the customized docker image name.
Apr 24, 2025
Lyrlark
changed the title
[bin/up] docker version failed to recongnise the customized docker image name.
[bin/up] docker-compose script failed to recongnise the customized docker image name.
Apr 24, 2025
Uh oh!
There was an error while loading. Please reload this page.
OS: CentOS 7.9
problem: Cannot save docker image with custominzed name(TAG)
description: Hi bros,I cannot customize the name of docker images, it said “ERROR: invalid version '5.4.0-with-texlive-xelatex-full-and-chinese-support'”,I just commit a new docker image by adding CN font and XeLaTeX full repair, naming the image "5.4.0-with-texlive-xelatex-full-and-chinese-support", only "a.b.c" name functioned, like 5.4.0 as well as the latest version of ShareLaTeX.
shell command: docker commit sharelatex sharelatex/sharelatex:5.4.0-with-texlive-xelatex-full-and-chinese-support
I will greatly appreciate it if someone tells me the reason, thx~
The text was updated successfully, but these errors were encountered: