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

Can't enter containers after rebooting the host #16

Closed
alxlg opened this issue Dec 6, 2021 · 5 comments
Closed

Can't enter containers after rebooting the host #16

alxlg opened this issue Dec 6, 2021 · 5 comments
Labels
bug Something isn't working

Comments

@alxlg
Copy link

alxlg commented Dec 6, 2021

Hi, I can create new containers and enter them just one time.

When I try to enter a container for a second time with

distrobox-enter --name fedora-35 -- bash -l  

Error: unable to start container "fedora-35": container create failed (no logs from conmon): EOF

Cannot start container, does it exist?
Try running first:

    distrobox-create --name <name-of-container> --image <remote>/<docker>:<tag>
An error occurred

despite I have a container with that name:

podman ps -a
CONTAINER ID  IMAGE                                 COMMAND               CREATED       STATUS                   PORTS  NAMES
92bef478ff04  registry.fedoraproject.org/fedora:35  /usr/bin/entrypoi...  15 hours ago  Created                         fedora-35-2
e276c55031e7  registry.fedoraproject.org/fedora:35  /usr/bin/entrypoi...  19 hours ago  Exited (6) 19 hours ago         fedora-35

EDIT: what's trigger this is the reboot of the host, I can create new containers and enter them as far as I don't reboot the host. After the reboot all the previous containers can't be entered despite they are listed by podman ps.

@alxlg alxlg changed the title Can't enter a container for a second time Can't enter containers after rebooting the host Dec 6, 2021
@89luca89
Copy link
Owner

89luca89 commented Dec 6, 2021

Hey @alxlg can you post a log with --verbose? thanks!

@89luca89 89luca89 added the bug Something isn't working label Dec 6, 2021
@89luca89
Copy link
Owner

89luca89 commented Dec 6, 2021

Also @alxlg can you check your podman version?

I saw that there is a bug on podman for version prior to 1.6.4 here: containers/podman#4522

@alxlg
Copy link
Author

alxlg commented Dec 6, 2021

@89luca89 podman version was 1.6.2 from Ubuntu 20.04 LTS repositories. I manually added the repository provided by Kubic project on Opensuse Build Service and got podman 3.4.2. Now I can indeed enter the containers.

Since it's a bug in outdated version of podman in Ubuntu LTS I guess you will just add a tip in the README to update podman in Ubuntu 20.04, no?

The commands I used are:

wget https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04/Release.key
sudo apt-key add Release.key
source /etc/os-release
sudo sh -c "echo 'deb http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_${VERSION_ID}/ /' > /etc/apt/sources.list.d/devel:kubic:libcontainers:stable.list"
sudo apt update -qq
sudo apt dist-upgrade

@89luca89
Copy link
Owner

89luca89 commented Dec 6, 2021

Yea I'm on 20.04 too and was wondering if it was an ancient podman version 😄

Ok will add a link to the podman installation site in the requirements
Will mark the issue as resolved
Thanks for the report!

@89luca89 89luca89 closed this as completed Dec 6, 2021
@89luca89
Copy link
Owner

89luca89 commented Dec 6, 2021

Added in commit: dcc5cbe5e796139783de79784c210c8e34c40396

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants