---
# System prepended metadata

title: rpm-ostree and ostree-rs-ext Issues

---

# rpm-ostree and ostree-rs-ext Issues 

I have tried to go over all the issues I discussed in my last meeting with @Colin Walters and tried to explain them to myself here. Feel free to collaborate here and answer these questions here.

## [ostree-rs-ext #153](https://github.com/ostreedev/ostree-rs-ext/issues/153) :
Example Usage
`ostree-ext-cli container image pull (container-registry: layered-image: tag)`
If the layered image is pulled from containers-storage library, then the pull command does not work. Hence, we need to get the config as a blob from the skopio#1495 first. 

#### Questions:
1. Does this imply that we can see the various diffids  from the config allowing us to fetch them by blob?

#### Answer:
1. Yes, the image configuration has the diffids.


## [ostree-rs-ext #154](https://github.com/ostreedev/ostree-rs-ext/issues/154) :
Example usage
`rpm-ostree ex-container export --repo=/ostree/repo #commit-id oci:/var/tmp/fcos:latest`
This converts an rpm-ostree commit to an oci format and places it in the /var/tmp/fcos:latest of the local system. Instead of adding a tag it interprets the tag as the name of the file. 

#### Questions:
1. Hence we need to ignore the :latest when doing mkdir -p and instead add it as a tag?

2. Is it not converted to OCI format if instead we execute this?
 `rpm-ostree ex-container export --repo=/sysroot/ostree/repo #commit-id docker://quay.io/myuser/pkg-name:tag`
 
#### Answer:
1. Yeah, we need to parse the image reference
2. The bug here is basically that for `oci:` directories we don't use `skopeo`.  The fix should land in  https://github.com/ostreedev/ostree-rs-ext/blob/main/lib/src/container/ocidir.rs

## [ostree-rs-ext #163](https://github.com/ostreedev/ostree-rs-ext/issues/163):
#### Questions:
1. How exactly are signatures for images tested? Does this mean simply generating a generating a key pair, signing with private and then testing the image with public to see if it matches? 

2. What does via proxy mean?

#### Answer:
1. Replied in issue
2. https://github.com/containers/containers-image-proxy-rs 

## coreos-layering-examples:
The command `ostree container commit` is RUN after making changes to the base FCOS image from a dockerfile. 

#### Questions:
1. What is this command doing and how does it differ from having a normal ostree commit? 

2. Does this generate a diff that can later be encapsulated/exported as a OCI formal container? (I thought any normal ostree commit could be converted to an layered container image? Does it have to be specifically generated with container commit?)

#### Answer:
1. (We really just need a man page for the tool upstream...)
2.
3.

## rpm-ostree #3992:
The apply-live does not prompt which services need to be restarted after the command which creates confusion. This is caused by the pkgdiff.n_removed() to fail.