![]() ![]() So how do I read the logs from the TeamCity server if it ever fails to initialise? As that's the ultimate goal here.ĭisclaimer: I'm an AWS noob and only use Linux when I have to. If this is the case then this should be made clear in the guide linked above (maybe this wasn't always the case?). I'm guessing this instance is just a proxy server and the other instance (without a public IP) is the actual TeamCity server. Neither Docker nor TeamCity seem to be installed. When I connect to that instance via SSH (the user is ec2-user - not core), it doesn't recognise Docker commands. Only 1 has a public IP address - the same one in the Outputs tab, below the HTTP address. TeamCity 2022.10 apporte l'activation de l'interface utilisateur Sakura par dfaut, de nombreuses nouvelles fonctionnalits lies au cloud, notamment le systme de gestion des informations d'identification AWS et l'accs terminal aux agents de build bass sur AWS EC2, et d'importantes amliorations aux intgrations VCS. There are 2 instances created by this template (I selected 0 agents). To see the logs, just run the docker logs command for the desired container.' 'To connect to the server’s console, you need to use your instance key: I successfully connected to TeamCity via HTTP by following the link in the Outputs tab.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |