containerd / containerd/nerdctl

[Compose] restart=always does not work properly

Open
#1,074 4 comments 3 reactions 1 assignee Claimed by @junnplus View on GitHub
kind/unconfirmed-bug-claim status/needs-more-information
Dominant language
Go
Stars
10.4k
Forks
826
Avg merge
1d 23h
Merged PRs (30d)
44

Description

### Description

Hi, I am experiencing an issue where I defined the `restart=always` param in the `docker-compose.yml`, but the container does not spin up at boot.

### Steps to reproduce the issue

1. Prepare a docker-compose.yml for the container

```yaml
version: "3.4"

services:
uptime-kuma:
image: louislam/uptime-kuma
container_name: uptime-kuma
restart: always
networks:
- proxy
volumes:
- /etc/uptime-kuma:/app/data
ports:
- 3001:3001

networks:
proxy:
name: proxy
```

2. Run `nerdctl compose up -d` to spin up the container

### Describe the results you received and expected

The container is able to spin up at its first launch with the `nerdctl compose up -d` command. However, when the machine is rebooted, the container stops and not able to spin up again.

I assume that `Nerdctl` inherits the generic feature of starting the container at boot if the `restart=always` param persists in the `docker-compose.yml`

### What version of nerdctl are you using?

0.17.0-beta.0

### Are you using a variant of nerdctl? (e.g., Rancher Desktop)

_No response_

### Host information

_No response_

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.