feat(docker/containers): new nvidia container toolkit

[dfldylan]

closes #3143
refactor #4791

Changes:

• based on master version 2.11.1
• add gpus use information on backend
• need to manual input the GPUs info at endpoint modification
• show GPUs use at dashboard and and containers list view
• add gpu support when create container (refactor code)
• show gpu command equivalent on container details view (refactor code)
• show available gpus when create container

[huib-portainer]

/azp run

[azure-pipelines]

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

[huib-portainer]

Looks like this needs a rebase...

[dfldylan]

Sure, give me some time

[dfldylan]

By the way, when is the next release?

[huib-portainer]

The next release actually is going to be next week.

[dfldylan]

@huib-portainer hello, I'm done. Please check.

• based on develop version (after 2.13)

[huib-portainer]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[huib-portainer]

Thanks for moving it all over and base it on the develop branch.
Currently there seems to be an issue with go test

portainer/api/datastore/migrate_data_test.go

Line 30 in df05914

func TestMigrateData(t *testing.T) {

[dfldylan]

Sorry, I do modify the backend definitions. Please check again. @huib-portainer

[huib-portainer]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[huib-portainer]

Unfortunately still no luck.

[dfldylan]

sorry ... just a extra space in json file

[azure-pipelines]

Commenter does not have sufficient privileges for PR 6872 in repo portainer/portainer

[huib-portainer]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[huib-portainer]

This can be tested by using the image portainerci/portainer:pr6872.

[huib-portainer]

The home screen now isn't loading for me:

[dfldylan]

@huib-portainer I clean my all env, and restart with portainerci/portainer:pr6872. But nothing wrong happened. Do you start in a new environment?

[huib-portainer]

Currently the tests are failing the build

[dfldylan]

sorry, please check

[huib-portainer]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[huib-portainer]

Actually, for the upgrade to work you'll also need to bump this one to 41

portainer/api/portainer.go

Line 1350 in ca30efe

DBVersion = 35

[dfldylan]

Actually, for the upgrade to work you'll also need to bump this one to 41

portainer/api/portainer.go

Line 1350 in ca30efe

DBVersion = 35

I found the db40 already exists.

[huib-portainer]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[huib-portainer]

@prabhat-org can you please advise?

Currently the build is failing because of

[prabhat83]

@dfldylan Since you have updated the DB version to 41, it has to be updated in the /api/datastore/test_data/output_35.json file like you have updated other properties. I know the name is confusing; we will change the name of the file to something like output_latest.json. The property name is version.DB_VERSION.

[dfldylan]

Previously, only free GPUs could be selected when creating containers. Now, All GPUs can be selected, with an added hint of whether they are occupied or not.

[huib-portainer]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[huib-portainer]

Thanks for bearing with us!
Upgrading an existing Portainer instance now works as well.

[dfldylan]

What should I do?

[huib-portainer]

Don't worry about the merge conflicts, we'll resolve those later.
We're aiming to release 2.14 this month and then pull this PR into the 2.15 release.
So we'll sort that out on our end.

[dfldylan]

Thank you!