Bug 1378080 - RFE: Add Docker Image for Developer Toolset 6 for toolchain
Summary: RFE: Add Docker Image for Developer Toolset 6 for toolchain
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Developer Toolset
Classification: Red Hat
Component: devtoolset-6-toolchain-container
Version: DTS 6.0 RHEL 7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: alpha
: 6.0
Assignee: Marek Polacek
QA Contact: Miloš Prchlík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-21 12:48 UTC by Honza Horak
Modified: 2016-11-15 12:32 UTC (History)
4 users (show)

Fixed In Version: devtoolset-6-toolchain-docker-6-2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-15 12:32:07 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2752 0 normal SHIPPED_LIVE new container image: rhscl/devtoolset-6-toolchain-rhel7 2016-11-15 17:31:34 UTC

Description Honza Horak 2016-09-21 12:48:45 UTC 
Description:
Tracker bug for addition of Docker Image for Developer Toolset 6 for toolchain

Proposed Docker image name:
  rhscl/devtoolset-6-toolchain-rhel7

Bugzilla component:
  devtoolset-6-toolchain-docker

Please, follow Docker Container Workflow:
  https://mojo.redhat.com/docs/DOC-1051868

When filling the Google form (https://docs.google.com/a/redhat.com/forms/d/e/1FAIpQLSdtqRDV7qG3oPZSXc_ioDyXXjf6UtUa4bPoUB6JwvW8D9lHbA/viewform), consider using these values:

  Image Type: Layered Image
  Defect Tracker Component: devtoolset-6-toolchain-docker
  Update Cadence: on base image rebuild (every 6 weeks)
  Product Line: RHSCL
  Image End-of-Life: same as devtoolset-6 SCL (Nov 01 2018?)
Comment 1 Marek Polacek 2016-09-21 12:59:52 UTC 
I've filed the Google form but I used Image Type: Base Image instead.  Is that a problem?
Comment 6 Miloš Prchlík 2016-11-04 11:42:30 UTC 
Verified, image exists and there's an erratum for it.
Comment 8 errata-xmlrpc 2016-11-15 12:32:07 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:2752
Note You need to log in before you can comment on or make changes to this bug.