fix: use logs instead of start -a for tty container in TestCreateWithTty

With -t, the container's output goes through a pseudoTTY. Attaching
via "start -a" does not reliably forward PTY output through Tigron's
subprocess pipe, causing the stty check to fail on certain containerd
versions (e.g. v1.7.30).

Match the original test's approach: start the container without -a,
then read its output via "nerdctl logs" which goes through the log
driver and is always available after the container exits.

Signed-off-by: Ogulcan Aydogan <ogulcanaydogan@hotmail.com>

Author: ogulcanaydogan

cmd/nerdctl/container/container_create_linux_test.go

@@ -288,20 +288,20 @@ func TestCreateWithTty(t *testing.T) {
 			Description: "create with tty - stty succeeds",
 			Setup: func(data test.Data, helpers test.Helpers) {
 				helpers.Ensure("create", "-t", "--name", data.Identifier(), testutil.CommonImage, "stty")
+				// start without -a: tty output is not forwarded over a pipe, so
+				// capturing it via "start -a" is unreliable. Use "logs" instead,
+				// which reads from the containerd log driver regardless of tty.
+				helpers.Ensure("start", data.Identifier())
 			},
 			Cleanup: func(data test.Data, helpers test.Helpers) {
 				helpers.Anyhow("container", "rm", "-f", data.Identifier())
 			},
 			Command: func(data test.Data, helpers test.Helpers) test.TestableCommand {
-				return helpers.Command("start", "-a", data.Identifier())
+				return helpers.Command("logs", data.Identifier())
 			},
 			Expected: func(data test.Data, helpers test.Helpers) *test.Expected {
 				return &test.Expected{
-					ExitCode: 0,
-					Output: func(stdout string, t tig.T) {
-						assert.Assert(t, strings.Contains(stdout, "speed 38400 baud; line = 0;"),
-							fmt.Sprintf("expected stdout to contain speed info: %q", stdout))
-					},
+					Output: expect.Contains("speed 38400 baud; line = 0;"),
 				}
 			},
 		},