Guest24897
/
DockerCLI
mirror of https://github.com/docker/cli.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
10,222 Commits 11 Branches 241 Tags 240 MiB
Commit Graph

7 Commits

Author SHA1 Message Date
Sebastiaan van Stijn 2088c5963b
vendor: github.com/docker/docker 1a1f3cff45ec (master, v27.0-dev) 
Rewrite local code to use the new container.Ulimit alias to start
transitioning away from direct uses of go-units.Ulimit.

full diff: https://github.com/docker/docker/compare/v27.0.0-rc.2...1a1f3cff45ec5aba4a520fae88b4f929eab8b3e8

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
 2024-06-20 13:04:54 +02:00
Sebastiaan van Stijn 866e4b10a1
opts/UlimitOpt: sort lists by name 
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
 2020-09-10 11:56:27 +02:00
Silvin Lubecki b3d4c6aac7
opts/ulimit_test.go:11:13: composites: `*github.com/docker/cli/vendor/github.com/docker/go-units.Ulimit` composite literal uses unkeyed fields (govet) 
Signed-off-by: Silvin Lubecki <silvin.lubecki@docker.com>
 2019-10-31 19:22:15 +01:00
Vincent Demeester 8b725e10e7 Clean some stuff from runconfig that are cli only… 
… or could be in `opts` package. Having `runconfig/opts` and `opts`
doesn't really make sense and make it difficult to know where to put
some code.

Signed-off-by: Vincent Demeester <vincent@sbr.pm>
 2017-05-15 11:57:20 +02:00
Daniel Nephin cef8b71ff4 Move ulimit options to runconfig opts 
Signed-off-by: Daniel Nephin <dnephin@docker.com>
 2017-05-15 11:57:17 +02:00
Shishir Mahajan f3841a1d27 Add and modify tests for legacy and new daemon invokations 
Signed-off-by: Shishir Mahajan <shishir.mahajan@redhat.com>
Signed-off-by: Tibor Vass <tibor@docker.com>
 2017-05-15 11:57:14 +02:00
Vincent Demeester 7b9ceadc4d Add test coverage to opts and refactor 
- Refactor opts.ValidatePath and add an opts.ValidateDevice
  ValidePath will now accept : containerPath:mode, hostPath:containerPath:mode
  and hostPath:containerPath.
  ValidateDevice will have the same behavior as current.

- Refactor opts.ValidateEnv, opts.ParseEnvFile
  Environment variables will now be validated with the following
  definition :
  > Environment variables set by the user must have a name consisting
  > solely of alphabetics, numerics, and underscores - the first of
  > which must not be numeric.

Signed-off-by: Vincent Demeester <vincent@sbr.pm>
 2017-05-15 11:57:14 +02:00