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
After having to upgrade the server, and having to connect /opt/teamcity/bin to my host, i eventually stopped the container and removed it , re-pulled teamcity-server image, and tried to re-use the same script for starting a new container. This time the container exited with an error on line 21, /opt/teamcity/bin/teamcity-server.sh not found or something like that
What version if TeamCity have you had before upgrade and what's after?
Maybe it fails because your script provides old bin directory to new TeamCity versions.
After having to upgrade the server, and having to connect /opt/teamcity/bin to my host, i eventually stopped the container and removed it , re-pulled teamcity-server image, and tried to re-use the same script for starting a new container. This time the container exited with an error on line 21, /opt/teamcity/bin/teamcity-server.sh not found or something like that
docker run -dit --restart unless-stopped --name teamcity-server \ -v /opt/teamcity/data:/data/teamcity_server/datadir \ -v /opt/teamcity/logs:/opt/teamcity/logs \ -v /opt/teamcity/bin:/opt/teamcity/bin \ -p 80:8111 \ jetbrains/teamcity-server &
after removing
-v /opt/teamcity/bin:/opt/teamcity/bin \
everything worked againThe text was updated successfully, but these errors were encountered: