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

errors about 'unmarshalling container' & 'invalid IP address' when starting container #1449

Closed
miabbott opened this issue Sep 12, 2018 · 2 comments
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@miabbott
Copy link
Contributor

/kind bug

After upgrading to Fedora 28 Silverblue 28.20180911.0, I started my pet container as usual, but received some errors while doing so. The errors were not fatal, but I wanted to report this behavior anyways.

$ sudo podman run --rm -it --privileged --net=host -v /srv:/srv -v /var/cache/dnf:/var/cache/dnf -v $HOME:$HOME -v /etc/localtime:/etc/localtime --dns=192.168.124.1 localhost/miabbott/myprecious:28
ERRO[0000] Error retrieving container 41c4711ec04f887a935b5958d4d474c5ce6781114655f57b6e1bfb581919380f from the database: error unmarshalling container 41c4711ec04f887a935b5958d4d474c5ce6781114655f57b6e1bfb581919380f config: invalid IP address: AAAAAAAAAAAAAP//wKh8AQ== 
ERRO[0000] Error retrieving container 8b032d08d4d576cecaf5266cdd29111ebe02fffc3bca640ed1cd92e45bba6b59 from the database: error unmarshalling container 8b032d08d4d576cecaf5266cdd29111ebe02fffc3bca640ed1cd92e45bba6b59 config: invalid IP address: AAAAAAAAAAAAAP//wKh8AQ== 

I built the image using buildah-1.3-1.git4888163.fc28.x86_64 and ran the container with podman-0.8.4-2.git9f9b8cf.fc28.x86_64

Nothing terribly interesting in the journal:

Sep 12 10:26:07 mastershake sudo[9594]: miabbott : TTY=pts/0 ; PWD=/var/home/miabbott ; USER=root ; COMMAND=/bin/podman run --rm -it --privileged --net=host -v /srv:/srv -v /var/cache/dnf:/var/cache/dnf -v /home/miabbott:/home/miabbott -v /etc/localtime:/etc/localtime --dns=192.168.124.1 localhost/miabbott/myprecious:28
Sep 12 10:26:07 mastershake audit[9594]: USER_CMD pid=9594 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='cwd="/var/home/miabbott" cmd=706F646D616E2072756E202D2D726D202D6974202D2D70726976696C65676564202D2D6E65743D686F7374202D76202F7372763A2F737276202D76202F7661722F63616368652F646E663A2F7661722F63616368652F646E66202D76202F686F6D652F6D696162626F74743A2F686F6D652F6D696162626F7474202D76202F6574632F6C6F63616C74696D653A2F6574632F6C6F63616C74696D65202D2D646E733D3139322E3136382E3132342E31206C6F63616C686F73742F6D696162626F74742F6D7970726563696F75733A3238 terminal=pts/0 res=success'
Sep 12 10:26:07 mastershake audit[9594]: CRED_REFR pid=9594 uid=0 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_localuser,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Sep 12 10:26:07 mastershake sudo[9594]: pam_systemd(sudo:session): Cannot create session: Already running in a session
Sep 12 10:26:07 mastershake sudo[9594]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 12 10:26:07 mastershake audit[9594]: USER_START pid=9594 uid=0 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Sep 12 10:26:07 mastershake systemd[1]: Started libpod-conmon-ad07a0c4c2d651ec345673ec17daa0302e00b50d482234a6c9864ee68460a9d6.scope.
Sep 12 10:26:07 mastershake systemd[1]: libcontainer-9677-systemd-test-default-dependencies.scope: Scope has no PIDs. Refusing.
Sep 12 10:26:07 mastershake systemd[1]: libcontainer-9677-systemd-test-default-dependencies.scope: Scope has no PIDs. Refusing.
Sep 12 10:26:07 mastershake systemd[1]: Created slice libcontainer_9677_systemd_test_default.slice.
Sep 12 10:26:07 mastershake systemd[1]: Removed slice libcontainer_9677_systemd_test_default.slice.
Sep 12 10:26:07 mastershake systemd[1]: libcontainer_9677_systemd_test_default.slice: Delegate=yes set, but has no effect for unit type
Sep 12 10:26:07 mastershake systemd[1]: libcontainer_9677_systemd_test_default.slice: Delegate=yes set, but has no effect for unit type
Sep 12 10:26:07 mastershake systemd[1]: Created slice libcontainer_9677_systemd_test_default.slice.
Sep 12 10:26:07 mastershake systemd[1]: Removed slice libcontainer_9677_systemd_test_default.slice.
Sep 12 10:26:07 mastershake systemd[1]: Started libcontainer container ad07a0c4c2d651ec345673ec17daa0302e00b50d482234a6c9864ee68460a9d6.
Sep 12 10:26:08 mastershake oci-umount[9696]: umounthook <debug>: prestart container_id:ad07a0c4c2d6 rootfs:/var/lib/containers/storage/overlay/4fd7cfbf82373079d8399599e43ac6d65a2f0fafcd76caf19b73866ee7e374e2/merged
Sep 12 10:26:18 mastershake dbus-daemon[1844]: [session uid=1000 pid=1844] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.50' (uid=1000 pid=2355 comm="/usr/libexec/tracker-miner-fs " label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023"
@mheon
Copy link
Member

mheon commented Sep 12, 2018

Those look like orphans from 0.8.1/0.8.2 from #1283

We don't have a good way of kicking them out of the state right now short of downgrading to 0.8.1 and doing a podman rm there

@miabbott
Copy link
Contributor Author

Finally got tired of seeing those error messages and downgraded to 0.8.2 to remove those containers. Worked like a charm.

@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 24, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

No branches or pull requests

2 participants