docker container exits immediately even with Console.ReadLine() in a .NET Core console application

If you switch your app to target .NET Core 2.0, you can use the Microsoft.Extensions.Hosting package to host a .NET Core console application by using the HostBuilder API to start/stop your application. Its ConsoleLifetime class would process the general application start/stop method.

In order to run your app, you should implement your own IHostedService interface or inherit from the BackgroundService class, then add it to host context within ConfigureServices.

namespace Microsoft.Extensions.Hosting{    //    // Summary:    //     Defines methods for objects that are managed by the host.    public interface IHostedService    {        // Summary:        // Triggered when the application host is ready to start the service.        Task StartAsync(CancellationToken cancellationToken);        // Summary:        // Triggered when the application host is performing a graceful shutdown.        Task StopAsync(CancellationToken cancellationToken);    }}

Here's a sample hosted service:

public class TimedHostedService : IHostedService, IDisposable{    private readonly ILogger _logger;    private Timer _timer;    public TimedHostedService(ILogger<TimedHostedService> logger)    {        _logger = logger;    }    public Task StartAsync(CancellationToken cancellationToken)    {        _logger.LogInformation("Timed Background Service is starting.");        _timer = new Timer(DoWork, null, TimeSpan.Zero,             TimeSpan.FromSeconds(5));        return Task.CompletedTask;    }    private void DoWork(object state)    {        _logger.LogInformation("Timed Background Service is working.");    }    public Task StopAsync(CancellationToken cancellationToken)    {        _logger.LogInformation("Timed Background Service is stopping.");        _timer?.Change(Timeout.Infinite, 0);        return Task.CompletedTask;    }    public void Dispose()    {        _timer?.Dispose();    }}

Then creating the HostBuilder and adding the service and other components (logging, configuration).

public class Program{    public static async Task Main(string[] args)    {        var hostBuilder = new HostBuilder()             // Add configuration, logging, ...            .ConfigureServices((hostContext, services) =>            {                // Add your services with depedency injection.            });        await hostBuilder.RunConsoleAsync();    }}

You should run your container in Interactive mode (with the -i option), but please note that the background processes will be closed immediately when you run the container, so make sure your script is run in the foreground or it simply won't work.

The only way I could get Docker/Linux to keep my .NET Core application alive was to spoof ASP.NET into hosting it for me... This is such an ugly hack!!

Doing it this way will run in Docker using the docker run -d option, so you don't have to have a live connection to keep the STDIN stream alive.

I created a .NET Core console application (not an ASP.NET app) and my Program class looks like this:

public class Program{    public static ManualResetEventSlim Done = new ManualResetEventSlim(false);    public static void Main(string[] args)    {        //This is unbelievably complex because .NET Core Console.ReadLine() does not block in a docker container...!        var host = new WebHostBuilder().UseStartup(typeof(Startup)).Build();                using (CancellationTokenSource cts = new CancellationTokenSource())        {            Action shutdown = () =>            {                if (!cts.IsCancellationRequested)                {                    Console.WriteLine("Application is shutting down...");                    cts.Cancel();                }                Done.Wait();            };            Console.CancelKeyPress += (sender, eventArgs) =>            {                shutdown();                // Don't terminate the process immediately, wait for the Main thread to exit gracefully.                eventArgs.Cancel = true;            };            host.Run(cts.Token);            Done.Set();        }    }      }

The Startup class:

public class Startup{    public void ConfigureServices(IServiceCollection services)    {        services.AddSingleton<IServer, ConsoleAppRunner>();    }    public void Configure(IApplicationBuilder app, IHostingEnvironment env)    {    }}

The ConsoleAppRunner class:

public class ConsoleAppRunner : IServer{    /// <summary>A collection of HTTP features of the server.</summary>    public IFeatureCollection Features { get; }    public ConsoleAppRunner(ILoggerFactory loggerFactory)    {        Features = new FeatureCollection();    }    /// <summary>Performs application-defined tasks associated with freeing, releasing, or resetting unmanaged resources.</summary>    public void Dispose()    {    }    /// <summary>Start the server with an application.</summary>    /// <param name="application">An instance of <see cref="T:Microsoft.AspNetCore.Hosting.Server.IHttpApplication`1" />.</param>    /// <typeparam name="TContext">The context associated with the application.</typeparam>    public void Start<TContext>(IHttpApplication<TContext> application)    {        //Actual program code starts here...        Console.WriteLine("Demo app running...");        Program.Done.Wait();        // <-- Keeps the program running - The Done property is a ManualResetEventSlim instance which gets set if someone terminates the program.    }}

The only nice thing about it is that you get to use DI in your application (if you want to) - so in my use case, I am using the ILoggingFactory to handle my logging.

Edit 30th Oct 2018
This post still seems to be popular - I'd like to just point out to anyone reading my old post that it is now pretty ancient. I was basing it on .NET Core 1.1 (which was new at the time). It is likely that if you are using a newer version of.NET Core (2.0 / 2.1 or greater) that there is probably a much better way of solving this problem now. Please take time to look at some of the other posts on this thread which may not be as highly ranked as this one, but may be newer and more up-to-date.