Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

container exits if /opt/teamcity/bin is mounted #19

Open
javahaxxor opened this issue Jan 15, 2018 · 1 comment
Open

container exits if /opt/teamcity/bin is mounted #19

javahaxxor opened this issue Jan 15, 2018 · 1 comment
Labels

Comments

@javahaxxor
Copy link

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 again

@VladRassokhin
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants