Troubleshooting

A build failed

Open the build. The jobs table shows which job failed (a red box in the graph) and links its log. Read the end of it: it says what Portage refused. Typical causes:

  • “USE changes are necessary” or a conflict between settings: the packages need a USE flag set a certain way. Add the line it suggests to the config’s package.use (see Choose how packages are built (configs)) and build again.

  • A package is masked or not keyworded for your architecture: ask for it in package.accept_keywords (www-client/firefox ~amd64), or choose a tree that has it unmasked.

  • A package is not in the tree: the form refuses it when you save, with a “did you mean”. The tree may be too old or too new.

  • Out of memory: large packages (browsers, compilers) need more. Raise Memory per job.

The page says Planning for a long time

Planning a whole system takes minutes. Follow the planner’s log live shows where it is. A tree that has not finished syncing delays it.

A job’s log says not kept

The repository the build uploads to has no upload proxy, so it keeps no logs. Use a repository with one.

The container will not start: “no such file or directory”

The entrypoint holds a whole command line on one line. Put only the program on the first line (/usr/sbin/nginx) and each argument on its own line in Cmd (see Make a container image).

nginx stops right away with getpwnam("nginx") failed

The image has no user database. Set User to 1000:1000 so it runs as an ordinary user.

Pushing the image fails

  • “unauthorized”: the login is wrong or for another host. A login is sent only to its own host; choose the one your registry made.

  • A server error (500/503) when the upload completes: the registry’s storage was busy. kaji tries again a few times by itself. If it still fails, press Retry on the container build.

I cannot see something my colleague made

Your role may not allow it, or it is private to them: keys and logins belong to the person who made them. Ask them to share it in your organization.

“already exists” when I save

Names are unique: the organization’s prefix plus the name. Another member of your organization may have used it. Choose another name.

The walk-through does not go on

It is waiting for a build that is still running, or for one that failed. The page says which. Open the build, fix it if it failed, and the tour carries on when it has succeeded. Resume the walk-through brings you back after you close it.