Skip to content

Random fixes for Image Building file #4172

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

Closed
wants to merge 2 commits into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions modules/administration/pages/image-management.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,7 @@ This section guides you through creating an ad-hoc activation key for this purpo

[NOTE]
====
To build a container, you need an activation key that is associated with a channel other than `SUSE Manager Default`.
To build a container, you need an activation key that is associated with a channel other than `SUSE Multi-Linux Manager Default`.
====

.Procedure: Creating an Activation Key
Expand Down Expand Up @@ -296,7 +296,7 @@ When you have selected a build profile, detailed information about the selected
[[at.images.docker.importing]]
=== Import an Image

The second way to build an image is to import and inspect arbitrary images.
The second way to get an image is to import and inspect arbitrary images.
To do that, select menu:Images[Image List] from the left navigation bar.
Complete the text boxes of the [guimenu]``Import`` dialog.
When it has processed, the imported image is listed on the [guimenu]``Image List`` page.
Expand Down
Loading