#1208 Container build(OSBS?) doesn't support UTF-8 characters in the Dockerfiles
Closed: Invalid 3 years ago by tkopecek. Opened 5 years ago by jcajka.


UTF-8 characters in Dockerfile do not seem to be an issue anymore in OSBS.
Following build use them in labels see:
* https://brewweb.stage.engineering.redhat.com/brew/buildinfo?buildID=1816684

lkolacek@archlinux ~ $ sudo podman inspect registry-proxy-stage.engineering.redhat.com/rh-osbs-stage/osbs-test-custom-
...
        "Labels": {
            "architecture": "x86_64",
            "authoritative-source-url": "registry.access.redhat.com",
            "build-date": "2020-04-17T00:55:09.309549",
            "com.redhat.build-host": "cpt-1004.osbs.stage.upshift.rdu2.redhat.com",
            "com.redhat.component": "osbs-test-hamburger-container",
            "com.redhat.license_terms": "https://www.redhat.com/en/about/red-hat-end-user-license-agreements",
            "distribution-scope": "private",
            "label-with-utf-chars-1": "míša",
            "label-with-utf-chars-2": "společenský",
            "name": "osbs-test/custom-label",
            "release": "1161",
            "url": "https://access.qa.redhat.com/containers/#/registry.access.redhat.com/osbs-test/custom-label/images/1.0.custom.label-1161",
            "vcs-ref": "c8ed784ebd6d54b01c943e2b2b1c3b53297960a7",
            "vcs-type": "git",
            "vendor": "Red Hat, Inc.",
            "version": "1.0.custom.label"
        },

Is there some environment, where is this still broken? #2105 should be possibly related (db has not set utf-8 as client encoding)

Metadata Update from @tkopecek:
- Custom field Size adjusted to None

4 years ago

Metadata Update from @tkopecek:
- Issue set to the milestone: 1.22
- Issue tagged with: bug, discussion

4 years ago

@tkopecek I haven't tried it yet. I will try to test it this week.

@jcajka any results? Otherwise I would like to close this ticket.

Metadata Update from @tkopecek:
- Issue set to the milestone: None (was: 1.22)

3 years ago

Metadata Update from @tkopecek:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata