Bug 2246836

Summary: Can't start a container
Product: [Fedora] Fedora Reporter: jacques
Component: moby-engineAssignee: Sergio Basto <sergio>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 39CC: copper_fin, go-sig, maxwell, mhofmann, sergio
Target Milestone: ---Keywords: Regression, Upgrades
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-10-29 16:46:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description jacques 2023-10-29 13:51:02 UTC
Can't start a container on F39 and Rawhide.

Reproducible: Always

Steps to Reproduce:
1.After a fresh install, add moby package rpm-ostree install moby-engine 
2.Add user to docker group
3.Start contenair.
Actual Results:  
docker run \
  -p 9000:9000 -p 9009:9009 -p 8812:8812 -p 9003:9003 \
  questdb/questdb:7.3.3
Unable to find image 'questdb/questdb:7.3.3' locally
7.3.3: Pulling from questdb/questdb
7dbc1adf280e: Pull complete 
f552638664bc: Pull complete 
4fa2bfb24291: Pull complete 
6cd966e10e18: Pull complete 
92b36a6f89ab: Pull complete 
4f4fb700ef54: Pull complete 
8e26b3f344b8: Pull complete 
Digest: sha256:006895788008c0bc749fb63e0e5989341588ba246a39b55883bbcb451e6273df
Status: Downloaded newer image for questdb/questdb:7.3.3
docker: Error response from daemon: failed to create task for container: failed to create shim task: ttrpc: cannot marshal unknown type: *task.CreateTaskRequest: unknown.
ERRO[0008] error waiting for container:                 


Expected Results:  
contenair up and running

It's working find on F38.
Rawhide have the same problem at Oct 29

Comment 1 jacques 2023-10-29 14:02:00 UTC
Important details :
 * I'm using silverblue version of FEDORA.

Comment 2 Sergio Basto 2023-10-29 16:46:27 UTC

*** This bug has been marked as a duplicate of bug 2237396 ***